After identifying performance concerns (since addressed in 2.65.0.2) while preparing 2.64 for a Long Term Support (LTS) package, we've decided not to publish a 2.64 LTS release.To avoid a long gap before the next LTS package, the 2.65 LTS release will be built on 2.65.3, so on-premise customers can upgrade directly from 2.63 LTS to 2.65 LTS. The 2.65 LTS packages will be available starting October 30.Please see our road map for the updated schedule.As always, please contact us — or reach out to your Customer Success Manager or Technical Account Manager for additional detail — with any questions or concerns.-Carl

We are delaying the 2.65.2 release to US Production to allow additional time to ensure quality. Originally scheduled for Thursday, September 10th, 2026, the new target date is Monday, September 14th, 2026. This delay does not affect the release timing for any of the other datacenters (EU, Canada, US Government Cloud, UK, or Australia).We appreciate your understanding and will keep you updated as we move forward.

The issue affecting our US Production environment, which began at approximately 6:40 AM CDT, was resolved at 8:00 AM CDT, and service is back to normal.We are still investigating the root cause(s) and will share more if there's anything further to report. We apologize for the disruption this caused and appreciate your patience.

We are aware of an issue affecting our US Production environment that began at approximately 6:40 AM CDT. 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.

Platform UpdateWe are planning no-downtime updates to deliver Platform release 2.65.2 to the following Production datacenters:US: Thursday, September 10thUS Government Cloud: Thursday, September 17thUK and Australia: Tuesday, September 22ndEurope and Canada: Wednesday, September 23rd 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 Friday, September 4th. (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, September 16th. MaintenanceWe will be performing no-downtime software maintenance on all Production servers (except US Government Cloud) between Tuesday, September 15th and Wednesday, September 16th. You can view the Maintenance Schedule for more information. As always, if you have any questions or concerns, ple

Your search experience is being upgraded today in US Build, Test, and UAT at 6 PM Eastern What's changing and whenToday, September 1, 2026, at 6 PM Eastern, Ideagen EHSQ Enterprise is rolling out an upgraded search experience across all US-hosted config areas — Build, Test, and UAT. This guide currently applies to those environments only; other regions will follow in a later phase. This upgrade does not touch your underlying records.During the rollout, the current and upgraded search versions run side by side ("dual feed") so the change can be switched on or off quickly if something doesn't look right. Questions?Reach out to your Customer Success Manager or Technical Account Manager.

Some US Production customers experienced errors when exporting to Excel, generating PDFs, or printing between approximately 10:38 AM and 11:10 AM CDT today, Friday, August 28, 2026. We apologize for the disruption this caused.This issue has been resolved, and export and print functionality is working as expected. No patch or further action is required.As a reminder, we're also deploying the 2.65.1.1 patch to US Production and US Government Cloud (FedRAMP) Production today, which is unrelated to this issue and addresses a separate problem with automated assignment emails.If you're still experiencing issues with exports or printing, please contact us so we can investigate further.As always, please contact us with any questions or concerns.-Carl

We're deploying a patch to US Production Friday, August 28, 2026, to fix an issue where automated assignment emails failed to send in certain cases (Search Notifications and custom emails configured from modules were unaffected). The issue originated with the 2.65.1.0 move to Production on Thursday, August 20th. The emails that failed to send will be re-sent to assigned users after the update.US Government Cloud (FedRAMP) Production will receive this patch on Friday, August 28th as well. Config (or Non-Prod) environments already running 2.65.1.0 will not be separately updated with this patch. Since this fix is narrowly scoped to assignment email delivery, we don't believe it's necessary to update Config ahead of the next scheduled Production release for each region.The release notes for this patch are available here.As always, please contact us with any questions or concerns.

Hi, I relevant new to Ideagen and heard you are able to set up Automated Report: Calculated Hours. I would like to set up weekly and monthly reports that automatic email to customers on their employee hours. Is there a QRG that can guide me through this process. If there have been previous reports set up. Is there any way to modify these reports? 

We want to follow up on yesterday's (Aug 17) service update with more detail on an issue that's been causing delayed search results in our US Production environment. We traced this to a scheduled background process that, under a period of unusually high traffic, became inefficient handling a large backlog of records. This put pressure on backend components responsible for keeping search indexes current, causing updates to lag behind. We've cleared the backlog and added processing capacity as an immediate fix. A code fix is scheduled to reach US Production this Thursday, Aug 20. We're also continuing root cause analysis on this alongside the Aug 5 incident, since the two turned out to be connected. If you believe specific records in your environment weren't reflected correctly in search during this period, please reach out to your CSM or TAM. They can help arrange to have those records refreshed. We know these delays were disruptive, especially for teams relying on up-to-date search res

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

We want to thank everyone who reported this morning's issue affecting some searches and logins in our US Production environment. We identified this as a recurrence of the August 5th incident. The affected service was restarted at approximately 9:36 AM Central time, and full operations have been restored. Some users may continue to see delayed search results for a short period while indexes catch up. If you're still experiencing search issues after 4:00 PM Central time, please reach out to your CSM. Our root cause analysis of the August 5th incident is ongoing, and we will be implementing additional safeguards as it concludes. Please watch our release notes for these improvements. We apologize for the disruption and appreciate your patience. --John

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.

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