Moveworks Outage History

We have identified an issue affecting the testing of compound actions in Agent Studio, where users may see a "Failed to process custom action" error. A fix is currently being deployed. This issue is limited to the testing experience only — compound actions already running in the assistant are not affected. We'll share another update once the fix has been rolled out and verified.

We're aware of an issue causing degraded search retrieval for Knowledge Base articles and files. Affected customers may see incomplete or missing content in search results. Our engineering team has identified the issue and is actively deploying a fix. We apologize for the disruption and appreciate your patience as we work to resolve this. We'll share updates as remediation progresses.

We're aware of an issue affecting Jira ITSM customers where tickets are not being automatically updated or resolved via the assistant. This is occurring intermittently during the ticket finalization step. Our team has identified the root cause and is deploying a hotfix. We appreciate your patience and will provide a follow-up update once this has been fully resolved.

We are continuing to work on a fix for this issue.

We have identified the issue and are currently working on deploying a fix. We will provide another update once the fix has been applied.

We are seeing some improvement, but failures are still occurring. We are actively working on a fix and will continue to provide updates.

We have identified an issue where the **View Permission** feature in Setup is currently returning an error instead of the expected results. Our team is actively working on a fix and will keep you updated on the progress. We apologise for the inconvenience caused and appreciate your patience in the meantime.

We are currently investigating an issue affecting User Identity Ingestion. Impacted customers may experience failures in user identity sync, which could affect AI Assistant access to new users dependent on up to date user data. Our engineering team has been engaged and is actively working toward a resolution. We will provide updates as more information becomes available.

We are continuing to investigate the issue affecting User Identity Ingestion. Our engineering team has identified that the failure occurs during the identity validation step when processing geocode information of users. Work is actively ongoing to resolve this. We will provide another update as soon as more information is available.

We have identified an issue where Live Agent Chat is not functioning for some users. Affected users are unable to be handed off to a live agent and may encounter an error when attempting to do so. We apologize for the inconvenience and are actively working to resolve this. Updates will be provided as they become available.

We have identified the issue and are currently pushing a fix. We will monitor closely and provide a further update once confirmed resolved. We appreciate your patience.

Microsoft has now published a Service Health Advisory (TM1260604) related to this issue. We are continuing to monitor updates from Microsoft and will share further information as it becomes available. Please follow the Microsoft Service Health Advisory (TM1260604) for the latest updates and progress on resolution via the Microsoft 365 Service Health dashboard. We appreciate your patience and will share updates as soon as more information becomes available

Microsoft has shared that their monitoring has detected an increase in failures when users attempt to interact with bots. They are currently analyzing these failures to better understand the issue and determine next steps toward identifying the root cause. We appreciate your continued patience as Microsoft investigates and works toward resolution.

Microsoft continues to actively work on this issue. Please follow the Service Health Advisory (TM1260604) for the most up to date information and progress toward resolution.

Microsoft’s initial findings indicate that a portion of the infrastructure supporting bots in Microsoft Teams is operating in a degraded state. They are attempting to restart affected components and redirect traffic to healthy infrastructure to help mitigate the issue.

We have identified an issue where the AI Assistant in the Microsoft Teams App Store is not responding to users. Our team is actively investigating and working to resolve this as quickly as possible. We appreciate your patience and will share updates as soon as more information becomes available

We have identified the root cause of the issue and are currently in the process of deploying a fix. Our team is actively pushing the necessary changes to restore full functionality for affected users. We will provide another update once the deployment is complete. Thank you for your continued patience.

We’re aware that some users may be experiencing difficulties accessing the AI Assistant in Gov Cloud. Our engineering team is actively investigating the issue and working on a resolution. We’ll provide updates as more information becomes available and appreciate your patience while we work to restore full service.

We have received acknowledgment of the issue from Microsoft and are actively collaborating with them to resolve it. We will share further updates as we have more information.

We have identified an issue preventing users from signing in to the My Moveworks portal. This appears to be affecting customers who use Ping Identity for authentication. We sincerely apologize for the inconvenience and are actively working to resolve the issue. We will provide updates as more information becomes available.

We are now also observing that this issue is impacting customers using non Ping Identity SSO providers as well. Our engineering teams are continuing to investigate and remediate the root cause.

We have identified an issue that is impacting some customers during ticket creation: although tickets are being created successfully, the process is failing when we attempt to fetch the ticket, resulting in the error “Unsupported Ticket type for reference ID …” and preventing the submission from completing. We apologize for the inconvenience this is causing, and our team is actively working on a fix to restore normal ticketing functionality as quickly as possible. Impacted Regions: US, EU, CA, AU