Samanage experienced a minor incident on January 28, 2026 affecting Application (North America) and Application (EMEA), lasting 18h 17m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 28, 2026, 07:54 PM UTC
We are investigating an issue where some users are unable to fully load service (catalog) requests. Affected pages may briefly appear and then show blank or incomplete content. Our engineering team is actively investigating the cause and working to restore full functionality. We will provide updates on this page as more information becomes available. If you are impacted and need assistance, please contact SolarWinds Support through your usual channels.
- investigating Jan 28, 2026, 08:08 PM UTC
We are continuing to investigate this issue.
- investigating Jan 28, 2026, 08:43 PM UTC
Our investigation has determined that this issue is limited to a subset of Service Desk service requests and service catalog items and does not affect all users or all catalogs. We are continuing to investigate the underlying cause and will provide additional updates on this page as our work progresses.
- identified Jan 28, 2026, 09:29 PM UTC
We have identified the root cause of the issue. It occurs when a process workflow includes a Send Notification action that sends an email to a user or email address that does not have a valid user account within the affected Service Desk instance. Our engineering team is actively working on a fix. Additional updates will be provided on this page as progress continues.
- identified Jan 28, 2026, 11:17 PM UTC
We are actively working on a fix for this issue. As a reminder, the cause occurs when a process workflow includes a Send Notification action that sends an email to a user or email address that does not have a valid user account in the affected Service Desk instance. As a temporary workaround, service desk administrators can update the affected workflows so that Send Notification actions are configured to send emails to a named user with a valid Service Desk account instead of an email address that is not associated with a user. We will provide further updates on this page as our work progresses.
- identified Jan 29, 2026, 01:41 AM UTC
Our engineering team has prepared a fix for this issue, and the deployment process has started. During the deployment window, some users may experience brief slowdowns or intermittent delays; we expect any impact to be minimal and temporary. We will provide a further update on this page once the deployment has finished.
- monitoring Jan 29, 2026, 03:30 AM UTC
Our Engineering team has successfully applied a fix and is applying it retroactively to resolve the issue for all affected users. Any interruptions during this process should be minimal. We will provide another update in the next hour.
- monitoring Jan 29, 2026, 05:38 AM UTC
Our Engineering team is continuously working on applying a fix to the data for all affected users. Further updates will be provided in the next hour.
- monitoring Jan 29, 2026, 08:19 AM UTC
Our Engineering team is actively deploying a remediation to address issues resulting in page load failures, blank pages, or incomplete content. Further updates will be provided as progress continues.
- monitoring Jan 29, 2026, 11:05 AM UTC
Our team is in the final stages of deploying the fix. We expect completion shortly and will share an update immediately.
- monitoring Jan 29, 2026, 11:28 AM UTC
The fix deployment is now complete, and our team is closely monitoring the results to ensure stability.
- resolved Jan 29, 2026, 02:12 PM UTC
We are marking this issue as resolved, as we have confirmed that all new service requests work correctly and previously submitted requests work as intended. If the issue resurfaces or if you require any further assistance, please don’t hesitate to contact us at [email protected].