Platform UpdateWe are planning no-downtime updates to deliver Platform release 2.65.1 to the following areas: US Production: Thursday, August 20thUS Government Cloud Production: Thursday, August 27thEurope and Canada Production: Wednesday, September 2nd You can review the release notes for an overview of the changes. ActionPlease report any unexpected behavior that you notice in your US Config (Build, Test, and UAT) areas, which we plan to update with this new version by Thursday, August 13th. (We will postpone the Production update if we're not confident in its quality.) This release will reach the European and Canadian Config areas on Wednesday, August 26th. MaintenanceWe will be performing no-downtime software maintenance on all Production servers between Tuesday, August 18th, and Thursday, August 20th as outlined in the Maintenance Schedule. As always, if you have any questions or concerns, please don't hesitate to contact us.

Early last week, we changed the sender/reply-to address for automated emails (notifications, reports, password resets, etc.) from @devonway.com to no-reply@ideagen.com, without enough advance notice. This change took effect across all commercial Production environments (US, EU, and Canada) by the end of last week. Many of you had customized reply-to addresses or filters built around your devonway.com address, and this change caused some organizations to stop receiving our emails. We're sorry for the disruption.Why: The devonway.com domain is being retired. Support ends August 21, 2026 — after that, no devonway.com address will work, regardless of what's in use today.Your options before August 21:Restore your previous @devonway.com address temporarily, to buy time before the final cutover. Move to @ideagen.com now, keeping your custom name (e.g. yourcompany@ideagen.com instead of the generic no-reply@) — this is the permanent destination.If you don't choose, your account stays on its cu

Update on EU/Canada Production: after further review, we've decided to hold off on deploying 2.65.0.1 to EU and Canada Production. Instead, we'll deliver 2.65.0.2 to those regions next week, which is cumulative and includes everything in 2.65.0 and 2.65.0.1, plus the additional fixes and improvements described in the release notes.We're deploying 2.65.0.2 to US Production on Tuesday, August 11th, to EU Production on Wednesday, August 12th, and to Canada Production on Thursday, August 13th.This release includes several targeted improvements to performance on the mobile and REST data sync path, particularly around search and reference-data syncing. Customers doing large reference-data syncs or high-volume searches should notice meaningfully faster response times and reduced data transfer.No action is needed on your end - these improvements will take effect automatically once this patch is live.As always, please contact us with any questions or concerns.-Carl

The issue affecting our US Production environment has been resolved. Service was restored at approximately 6:20 AM Pacific time. We will be undertaking a structured root cause analysis review to understand the exact cause of the issue and will be implementing mitigation actions to prevent future occurrences. We apologize for the impact and thank you for your patience. -Zack

We're deploying a patch to US Production today, Monday, August 3, 2026, to fix two related issues causing elevated server resource usage and slower response times under heavy load.Given the improvement this brings, we're also moving up delivery of this release to EU/Canada Production, from the previously scheduled August 12th to Thursday, August 6th. This release will go to EU/Canada Config today.US Government Cloud (FedRAMP) Production will receive this patch on Friday, August 7th, with Config updated tomorrow, Tuesday, August 4th.The release notes for this patch are available here.No action is needed on your end - performance under load will improve once this patch is live.As always, please contact us with any questions or concerns.-Carl

On Tuesday, August 4th, we'll be taking US Commercial non-production environments offline for approximately 60 minutes as part of scheduled maintenance, which is different than our typical scheduled maintenance windows (Tuesdays, 4–5 PM PT) that do not require any downtime.This maintenance will take place from 4:00 PM to 5:00 PM PT and is needed to complete some remaining migration-related work.What this means for you:This affects non-production areas only — production environments are not impacted. Non-production environments will be unavailable for up to one hour during the stated window. If you have testing, validation, or project work planned in non-production during this time, please plan accordingly.We apologize for any inconvenience this may cause. If you have any questions or concerns, please reach out to your CSM or TAM.Thank you for your understanding.- Carl

Platform UpdateWe are planning no-downtime updates to deliver Platform release 2.65.0 to the following areas:US Production: Thursday, July 30th US Government Cloud Production: Thursday, August 6th Europe and Canada Production: Wednesday, August 12thYou can review the release notes for an overview of the changes.ActionPlease report any unexpected behavior that you notice in your US Config (Build, Test, and UAT) areas, which we are updating with this new version on Monday, July 27th. (We will postpone the Production update if we're not confident in its quality.) This release will reach the European and Canadian Config areas on Wednesday, August 5th.As always, if you have any questions or concerns, please don't hesitate to contact us.-Carl

We're deploying a patch to US Production and US Government Cloud (FedRAMP) Production on Thursday, July 23, 2026, to fix an issue where users could potentially see records outside their assigned Reporting Authority in listings such as Recently Created Items, even though those records could not be opened directly.This patch will be included in the 2.64.4 release going to EU/Canada Production on Wednesday, July 29, 2026, as already scheduled. It will also be included in the 2.64 LTS release for on-premise customers.The release notes for this patch are available here.No action is needed on your end - Reporting Authority scoping will be corrected across these listings once this patch is live.As always, please contact us with any questions or concerns.-Carl

We're deploying a patch to US Production this afternoon, Tuesday, July 21, 2026, to fix an issue with the batched email delivery introduced in 2.64.4. Emails being split into batches of 50 recipients or fewer were, in some cases, being sent in quick succession, which could cause some recipients to not receive their email due to a send-rate limit enforced by our email provider.2.64.4.1 adds a short pause between email batches so all batches stay under this rate limit and all intended recipients receive their email as expected.This patch is already included in the 2.64.4 release being deployed to EU/Canada Production, so no separate action is needed there.No action is needed on your end going forward - this is a backend fix and email delivery will continue to work as described in our 2.64.4 release notes. If you believe a notification failed to reach some recipients prior to this fix, please reach out to your Customer Success Manager or Technical Account Manager, who can help identify an

What you need to know We will be migrating our FTP server to new infrastructure. This is part of our ongoing effort to improve the reliability, performance, and security of our platform. When is this happening? The migration is scheduled for Tuesday, July 21st at 4:00 PM Pacific. Why are we doing this? This move gives us a more modern and resilient foundation for file transfer services, supporting better reliability and performance going forward. What is the expected impact? We do not expect any interruption to file transfer service during this migration. This has been planned and tested with that goal in mind. We expect the transition to take about 30 minutes. Do you need to do anything? No action is required. Your login credentials, usernames, and access permissions will remain unchanged. If you have any questions, please reach out to your customer success contact.

In last week's post about the 2.64.3.2 patch, we mentioned that 2.64.4 was being retargeted to Thursday, July 16th, 2026, for US Production, to keep a clean buffer around the July 10th infrastructure migration. That release is on track for Thursday, July 16th. It's been running in US Config since Monday, June 29th, and includes a fix for an issue some of you may have run into since the migration.Email recipient limit fixOur new infrastructure uses a different email delivery service that enforces a hard limit of 50 recipients per email - our previous environment did not have this limit. As a result, since the July 10th migration, emails sent to more than 50 recipients at once have not gone out as expected.2.64.4 includes a fix that automatically splits any email with more than 50 recipients into batches of 50 or fewer, so all intended recipients still receive it. One thing to note: when a distribution has more than 50 recipients, it's split into multiple emails so each batch stays under

We're pleased to confirm that the US Production infrastructure migration completed successfully this morning, within the planned maintenance window. What happenedThe migration proceeded as scheduled. Users were able to log in and resume normal activity within the maintenance window. We are continuing to validate systems in the background to ensure everything is fully confirmed and will follow up if any further action is needed. What this means for youUS Production is now running on the new infrastructure. Integrations, scheduled jobs, reporting, and background processes are all confirmed to be functioning as expected. If you had our previous IP address (67.192.92.50) whitelisted, please make sure you've updated your firewall or routing rules to allow 15.197.248.93 and 76.223.46.100. If you haven't made this change yet, please do so as soon as possible to avoid disruption.Thank youThank you for your patience during this migration window. This move gives us a more resilient and flexible

What you need to knowNext month, we will be migrating our US production environment to new infrastructure. This is the final phase of a multi-stage process — we have already completed and validated migrations of our Build/Test and UAT environments, so we are confident in the approach heading into production. When is this happening?The migration is scheduled for July 10th from 12:00 AM to 8:00 AM EDT. That window is intentionally conservative — we expect to complete the work well before 8:00 AM. Why are we doing this?This move gives us a more flexible and resilient foundation, which means better reliability and service delivery for you going forward. What is the expected impact?There will be a planned downtime of up to 8 hours during the migration window. We will be working to minimize that as much as possible. Do you need to do anything?For most customers, no action is required. However, if you have our IP address whitelisted in your firewall or routing rules — or if any third-party sy

We're deploying a patch to US Production and EU/Canada Production this Monday, July 6, 2026, to fix two export-related issues: one where grid and report exports were being capped at 5,000 rows regardless of the configured maximum row export limit, and another that prevented exports from completing when a "Date Created" filter used the "Is Between" operator. US Government Cloud (FedRAMP) Production will receive this patch the following day, Tuesday, July 7, 2026.The release notes for this patch are available here.If you need either of these fixed before Monday, please reach out to your Customer Success Manager or Technical Account Manager for details, as there are workarounds available in the meantime. As a preview: for the row limit issue, generating the data through a custom report (Chart icon > Other) rather than a standard grid export avoids the limitation. For the "Is Between" filter issue, if you're on Miramar, you can get the same result using Custom Filters with a combination

We're deploying a patch to US Production during the afternoon of Thursday, June 25, 2026, to resolve some module caching issues, as well as an issue with certain search notifications and grid exports. Because of this patch, we're delaying delivering 2.64.3 to the EU/Canada Production and GovCloud Production data centers until Monday, June 29, 2026.  The release notes for this patch are available here. As always, please contact us with any questions or concerns.

We're releasing version 2.64.4 of Ideagen EHSQ Enterprise on 25 June 2026.Here's what's improved.What's newFaster record creation from the dashboard — the old buried “Create New” button has been replaced with a role-tailored Quick Create toolbar at the top of each dashboard, giving users one-click access to their most-used record types (e.g. New Incident, New Permit) without navigating away. Admins configure which buttons appear per dashboard and per team. Cleaner, less cluttered screens — the record initiation screen now hides the nav rail, breadcrumbs, and excess controls so users can focus on filling in the form. Required fields now show a progress bar (“1 of 14 complete”) with a dropdown that jumps directly to any outstanding field, replacing the old competing side panel. Admins get new configuration power (act before go-live on 25 June 2026) — Quick Create toolbars, org logo white-labelling in the header, module icons/colours in the Create New modal, and a new “Grid: Button Menus”

As we continue final preparations for the 2.64.3 release, we want to ensure our team has adequate time to complete thorough validation before deployment. To accommodate this, we are updating the release schedule:US Production: Thursday, June 18th EU / Canada: Wednesday, June 24th GovCloud (FedRAMP): Thursday, June 25thWe recognize this has been a longer road than expected and appreciate your patience. Our priority is a smooth, stable deployment and we'd rather move the date than rush it. Please don't hesitate to reach out with any questions.

Our team has identified a module caching issue that requires additional time to resolve. Because of this, we are moving the 2.64.3 US Production release to Tuesday, June 16th. The EU and Canada release remains on schedule for Wednesday, June 17th. We would rather take that time now than introduce a problem into your production environment. Thank you for your continued patience, and please reach out if you have any questions or concerns.

The issue affecting our US Production environment has been resolved. Service was restored at approximately 12:00 PM Pacific time.We will be sharing a follow-up post with more details on the root cause. We apologize for the disruption and thank you for your patience.

We are aware of an issue affecting our US Production environment that began at approximately 11:30 AM Pacific time. Our team is actively investigating and working to restore normal service as quickly as possible.We will provide updates as we have more information to share. We apologize for the disruption and appreciate your patience.

We are delaying the 2.64.3 release to US Production by one week to allow additional time to ensure quality. The new target date is Thursday, June 11th, 2026. For EU and Canada customers, your environments have not received the 2.64.2 release or its subsequent patches as we've worked through the US environment's production issues. Given that, we have decided to skip the 2.64.2 release entirely and move directly to 2.64.3 which is currently scheduled for Wednesday, June 17th.  We appreciate your understanding and will keep you updated as we move forward.

After the rollout of our latest release to US production, we identified performance issues that need to be addressed before we proceed with the EU and Canada deployments.We are delaying those releases while we resolve and validate the fix. The EU and Canada datacenters will receive the release on June 3, 2026.Thank you for your patience while we get this right.

This afternoon (May 27, 15:30–16:15 CDT) we deployed a set of targeted improvements to our US Production environment intended to address what we believe to be the primary contributors to the slower response times reported since the 2.64.2 release on May 15. There was some service interruption during the deploy window itself, which a few of you may have noticed; the environment settled shortly after 16:15 CDT.Early indications since the deploy are encouraging. Common actions like Open, Save, and Submit are responding more quickly than they were over the past several days. We want to be transparent, however: monitoring continues, and it is still possible that response times will not fully return to the levels customers experienced prior to 2.64.2. If that is the case, our investigation will continue.As with the prior update, the European and Canadian data centers remain on the previous release and are unaffected by both the original regression and the changes we have now applied to US. W

We are aware that some users on US Production have experienced slower-than-expected response times for common actions like Open, Save, and Submit since the 2.64.2 release on May 15. This is our team's top priority.Our engineers are actively profiling the affected services in production and progressively eliminating potential causes. We are making steady progress, but we want to be careful about announcing a specific fix until our analysis is conclusive.Customers in the European and Canadian data centers are not affected, as those environments are still on the previous release. We will not deploy 2.64.2 to those regions until we have a clear understanding of the issue and confidence in a resolution.We will post an update here as soon as we have something concrete to share. As always, please contact us with any questions.