Moveworks Outage History
Moveworks is up right nowPingoru has recorded 51 incidents for Moveworks: 49 in the last 12 months and 17 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 1 of 720 (0%) |
| May 2026 | 4 | 5 of 744 (1%) |
| June 2026 | 7 | 212 of 720 (29%) |
| July 2026 | 2 | 208 of 744 (28%) |
| August 2026 | 6 | 442 of 744 (59%) |
| September 2026 | 7 | 400 of 720 (56%) |
| October 2026 | 3 | 8 of 527 (2%) |
Incidents, newest first
Minor October 15, 2026 Tool Studio Admins Unable to Edit Connectors or Script Actions 3h 37m Plugins Workspace, Connectors
Started Oct 15, 2026, 06:22 PM UTC· resolved Oct 15, 2026, 10:00 PM UTC
- identified Oct 15, 2026, 06:22 PM UTC
We have identified an issue affecting Tool Studio admins. Admins are seeing a “You do not have the role needed to perform this action” error when creating or updating connectors, and Script Actions in Agent Studio are failing to load, even though their permissions are configured correctly. Our engineering team is investigating the root cause and actively working on a fix. We don’t have a workaround yet, and we will share the next update as soon as we have more information. Impacted Regions: All
- identified Oct 15, 2026, 06:52 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 15, 2026, 07:46 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 15, 2026, 10:00 PM UTC
This incident has been resolved.
Minor October 1, 2026 Duplicate Employee Communications Messages on Microsoft Teams 2h 47m Employee Communications
Started Oct 01, 2026, 06:17 PM UTC· resolved Oct 01, 2026, 09:05 PM UTC
- identified Oct 01, 2026, 06:17 PM UTC
We have identified an issue where some users are noticing duplication of Employee Communications campaign messages on Microsoft Teams. Messages continued to be delivered multiple times even after campaigns were cancelled, resulting in a degraded user experience. We sincerely apologize for the inconvenience.
- monitoring Oct 01, 2026, 07:38 PM UTC
We learned that some users also experienced intermittent delays and "thinking" messages in the Moveworks Assistant on Microsoft Teams due to the same underlying issue. We have now applied a mitigation and are actively monitoring the results. Thank you for your patience.
- resolved Oct 01, 2026, 09:05 PM UTC
This incident has been resolved as of 12:10 PM PST.
Critical October 1, 2026 Moveworks Assistant in Microsoft Teams Not Responding 1h 48m Microsoft Teams
Started Oct 01, 2026, 03:20 PM UTC· resolved Oct 01, 2026, 05:09 PM UTC
- investigating Oct 01, 2026, 03:20 PM UTC
We're investigating an issue affecting the Moveworks Assistant in Microsoft Teams. Users report the bot entering a "thinking" state with no response. In some cases, users are not receiving responses as expected. We are actively working on resolving this issue and will provide updates shortly. We apologize for the inconvenience caused.
- investigating Oct 01, 2026, 03:56 PM UTC
We are continuing to investigate and identify a mitigation. We sincerely apologize for the ongoing disruption.
- monitoring Oct 01, 2026, 04:11 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 01, 2026, 05:09 PM UTC
This incident has been resolved.
Minor September 28, 2026 Intermittent Error Responses in the Moveworks Assistant on EmployeeWorks Web App 4h 49m Moveworks AI Assistant, EmployeeWorks Web App
Started Sep 28, 2026, 08:33 PM UTC· resolved Sep 29, 2026, 01:23 AM UTC
- identified Sep 28, 2026, 08:33 PM UTC
We are investigating an issue affecting a small number of users of the Moveworks Assistant on the EmployeeWorks web app. Impacted users may receive the message "Looks like I am having some trouble responding to you now..." in response to their requests. The large majority of conversations are unaffected. Our engineering team has identified the component involved and is actively working on a fix. We will share another update as soon as remediation is underway or when we have more information. We apologize for the inconvenience and appreciate your patience.
- identified Sep 28, 2026, 08:38 PM UTC
We are continuing to work on a fix for this issue.
- identified Sep 28, 2026, 10:06 PM UTC
Our engineering team has identified a likely cause of the intermittent error responses affecting a small number of users of the Moveworks Assistant on the EmployeeWorks web app. We applied a configuration change and we have not observed the error since then. We are continuing to monitor the results through the end of the day to confirm the issue is fully resolved. We will share another update once we have confirmed the fix or if we have more information.
- resolved Sep 29, 2026, 01:23 AM UTC
This incident has been resolved.
Minor September 23, 2026 Agent Studio: Plugins page not loading for some roles 1h 35m Plugins Workspace
Started Sep 23, 2026, 02:57 PM UTC· resolved Sep 23, 2026, 04:33 PM UTC
- identified Sep 23, 2026, 02:57 PM UTC
We're aware of an issue where some users can't load the Agent Studio plugins page. They see the message "You do not have the role needed to perform this action." The issue affects users without Super Admin access in some orgs. We've identified the cause, and a fix is being deployed now. We'll share an update once it's resolved. Thanks for your patience.
- monitoring Sep 23, 2026, 04:07 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 23, 2026, 04:33 PM UTC
This incident has been resolved.
Notice September 21, 2026 Moveworks Academy Access Issue 19h 32m
Started Sep 21, 2026, 05:22 PM UTC· resolved Sep 22, 2026, 12:54 PM UTC
- identified Sep 21, 2026, 05:22 PM UTC
We have identified an expired SSL certificate affecting access to Moveworks Academy. Users may encounter a browser security warning that prevents them from accessing the site. The issue has been escalated to the relevant team for certificate renewal. We will share further updates as they become available.
- identified Sep 22, 2026, 02:18 AM UTC
We are continuing to work with the relevant team to restore access to academy.moveworks.com. We apologize for the inconvenience.
- resolved Sep 22, 2026, 12:54 PM UTC
We have rotated the SSL certificate and confirmed that access to Moveworks Academy has been restored. Users should now be able to access the site without browser security warnings. Thank you for your patience.
Minor September 17, 2026 Knowledge Ingestion Delays 2h 47m Enterprise Search
Started Sep 17, 2026, 08:15 PM UTC· resolved Sep 17, 2026, 11:03 PM UTC
- investigating Sep 17, 2026, 08:15 PM UTC
We are investigating an issue preventing scheduled knowledge ingestion jobs from running in the US region. As a result, the latest content may be delayed in being ingested. We apologize for the inconvenience. The Assistant remains available and functional. Other regions are unaffected.
- monitoring Sep 17, 2026, 09:46 PM UTC
A fix has been deployed and we are currently monitoring the results.
- resolved Sep 17, 2026, 11:03 PM UTC
This incident has been resolved.
Minor September 16, 2026 Get Help options not appearing for greeting messages 53m Live Agent Message Brokering
Started Sep 16, 2026, 05:21 PM UTC· resolved Sep 16, 2026, 06:14 PM UTC
- investigating Sep 16, 2026, 05:21 PM UTC
We are investigating an issue where any utterance that is identified as a greeting fails to render the help options on the Get Help page, leaving users unable to file a ticket or connect to a live agent. The Get Help tab opens but shows only the Chat Summary with no handoff options presented. We apologize for the inconvenience this is causing your users. Impacted Regions: All
- identified Sep 16, 2026, 05:40 PM UTC
We have identified that this is impacting customers on the Frontier and Standard tiers of the Model Upgrade program. We are actively working on a fix and will provide further updates shortly.
- resolved Sep 16, 2026, 06:14 PM UTC
A fix has been deployed and the Get Help options are now rendering as expected for all messages. Thank you for your patience, and apologies again for the disruption.
Major September 10, 2026 My Moveworks portal login not working 3h 30m Moveworks Setup, Moveworks Documentation, Support, Community
Started Sep 10, 2026, 04:48 AM UTC· resolved Sep 10, 2026, 08:19 AM UTC
- investigating Sep 10, 2026, 04:48 AM UTC
We are investigating an issue where users are not able to log in to the My Moveworks portal. We will keep you posted on the progress we make. We apologise for the inconvenience in the meantime.
- monitoring Sep 10, 2026, 05:27 AM UTC
A fix has been implemented, and we are monitoring the results.
- resolved Sep 10, 2026, 08:19 AM UTC
This incident has been resolved.
Minor September 4, 2026 Unable to send messages to the AI Assistant on MS Teams 22d Microsoft Teams
Started Sep 04, 2026, 12:17 PM UTC· resolved Sep 26, 2026, 12:32 PM UTC
- investigating Sep 04, 2026, 12:17 PM UTC
We have been seeing issues with a few users being unable to send messages to the Assistant on Teams. They see the chat bar being greyed out, which shows a message: "You cannot send messages to this bot". We are investigating the issue and are also working with Microsoft internally. At a high level, it looks like a policy update has blocked this bot from being accessible. We will keep you posted on the updates.
- identified Sep 04, 2026, 01:09 PM UTC
Workaround Available We have identified that, for some affected customers, the Available to setting for the Moveworks bot in the Microsoft Teams admin centre is set to No one. Restoring the appropriate availability has resolved the issue for some customers. Teams administrators can update this setting by following these steps: 1. Sign in to the Microsoft Teams admin centre. 2. Go to Teams apps → Manage apps and select the Moveworks bot. 3. Open the Users and groups tab. Alternatively, select No one (org-wide default) if it appears as a link. 4. Under Availability, select Edit availability. 5. Change Available to from No one to one of the following: Everyone — Select this if all users in the tenant should have access to the bot. This is the most common setting for Moveworks deployments. Specific users or groups — Select this to restrict access to particular security groups, Microsoft 365 groups, dynamic membership groups, or distribution lists. Search for and add the required users or groups. 6. Select Apply to save the change. Microsoft advises that availability changes can take up to 24 hours to apply to all users and, in rare cases, up to six days to appear in the Teams client. However, the change may take effect sooner. After allowing sufficient time for propagation, affected users should completely sign out of Microsoft Teams and sign back in to refresh their access. We are continuing to investigate the underlying cause and will provide further updates as more information becomes available.
- resolved Sep 26, 2026, 12:32 PM UTC
This incident has been resolved. Anyone still affected can follow the workaround steps shared previously.
Minor August 20, 2026 Assistant not responding in Microsoft Teams 1d 2h Moveworks AI Assistant
Started Aug 20, 2026, 02:55 PM UTC· resolved Aug 21, 2026, 05:20 PM UTC
- investigating Aug 20, 2026, 02:55 PM UTC
We are seeing intermittent failures on outbound calls to Microsoft Teams, which may result in the Assistant not responding in Teams. There is currently an elevated volume of reported Microsoft Teams issues, and we are actively investigating whether this is the cause. Impact: Assistant messages in Microsoft Teams may intermittently fail to deliver, and users may not receive a reply. Impacted regions: All We will keep you posted with further updates.
- monitoring Aug 20, 2026, 02:58 PM UTC
Error rates on outbound calls to Microsoft Teams are declining and the Assistant is responding normally for most requests. We are continuing to monitor to confirm full recovery.
- resolved Aug 21, 2026, 05:20 PM UTC
The intermittent unresponsiveness of the AI Assistant in Microsoft Teams has been resolved. Responses have returned to normal, and we have confirmed stability through continued monitoring. No further action is required from customers.
Minor August 19, 2026 Custom AI Assistant Logo Reverting to Moveworks Default (Microsoft Teams) 37d 22h Microsoft Teams
Started Aug 19, 2026, 02:21 PM UTC· resolved Sep 26, 2026, 12:36 PM UTC
- identified Aug 19, 2026, 02:21 PM UTC
We're investigating an active issue where end users in Microsoft Teams are seeing the default Moveworks logo instead of their organization's custom bot logo, despite a custom icon being set in the app manifest. This appears to affect the bots published via the Teams App Store (store auth) rather than a single tenant. Logging out/back in or clearing the Teams cache resolves it for some users. Our engineering team is actively investigating and we will share more details as they become available.
- identified Aug 20, 2026, 12:10 AM UTC
We have escalated this issue to Microsoft and are actively working with their team to address the issue. We will provide more details when they are available.
- monitoring Aug 20, 2026, 04:39 PM UTC
Microsoft has identified the root cause as a platform regression affecting app branding display in Teams. A mitigation has been deployed and is currently rolling out. Microsoft's engineering team continues to monitor the rollout and validate the fix. Users may see the correct custom logo restored as the mitigation propagates. No action is required on your side. We will continue to monitor and will share additional updates as progress continues.
- monitoring Sep 01, 2026, 05:16 PM UTC
Microsoft's mitigation continues to roll out and we are monitoring propagation. Most users should see the correct custom logo restored. If any users are still seeing the default Moveworks logo, please capture a HAR file while reproducing the issue and share it with Moveworks Support. We will share additional updates as progress continues.
- monitoring Sep 15, 2026, 07:18 PM UTC
Issue summary and resolution details from Microsoft: Issue: Some published Teams apps briefly displayed the app publisher's default icon instead of the custom icon/branding configured by the tenant admin. Root Cause: A recent platform change to how bot-based interactions authenticate could, in certain cross-tenant request paths, cause the service to look up the tenant's data in the wrong geographic region. When that lookup did not resolve, the service temporarily cached an incomplete view of the tenant's app-customization settings. While that cached view was in effect, affected apps fell back to the publisher's default icon rather than the configured custom branding. The actual configuration was never lost — it remained correct in the source of record; only the temporary cached copy was incomplete. Onset timeframe: Introduced with the bot PFT/POP rollout in the July timeframe. Exact rollout start/ramp dates are being confirmed with the partner team that owns the rollout. Resolution: We have corrected the region-resolution logic so tenant-specific data is always looked up using the tenant's own region, preventing the incomplete cached state. The fix is rolling out through our standard deployment pipeline. As caches refresh, affected apps return to displaying the configured custom icons automatically, with no action required on the customer's side. Customer impact / data safety: Display-only regression. No configuration was changed or lost, and there was no impact to data security or access control. Mitigation timeline: • Code review / validation complete: Thursday EOD (9/11) • Server-side fix deployed via regular deployment process: 9/24 • Client cache refresh (~24 hours after server deployment): +24h • Fully reflected for customers: 9/25 Recovery is automatic as caches refresh post-deployment; no action is required from the customer.
- resolved Sep 26, 2026, 12:36 PM UTC
The fix should now be reflected for everyone, allowing the incident to be closed out.
Minor August 11, 2026 Issue Affecting Approval Requests 20h 52m Enterprise Approvals
Started Aug 11, 2026, 05:45 PM UTC· resolved Aug 12, 2026, 02:38 PM UTC
- monitoring Aug 11, 2026, 05:45 PM UTC
We identified an issue affecting multiple customers where approval requests were processed successfully, but users encountered a “You don’t have access to the request” error when retrieving the updated record. Engineering has deployed a fix and is currently monitoring the system to ensure stability. We will share additional updates as they become available.
- resolved Aug 12, 2026, 02:38 PM UTC
This incident has been resolved.
Notice August 10, 2026 Documentation site is down 4h 47m Moveworks Documentation
Started Aug 10, 2026, 12:46 PM UTC· resolved Aug 10, 2026, 05:33 PM UTC
- investigating Aug 10, 2026, 12:46 PM UTC
Our documentation site is currently down; we are working with the vendor to get it back up and running. We sincerely apologise for the inconvenience in the meantime.
- monitoring Aug 10, 2026, 12:53 PM UTC
The fix has been implemented, the site is loading fine now, and we are continuing to monitor it.
- resolved Aug 10, 2026, 05:33 PM UTC
This incident has been resolved.
Notice August 3, 2026 CSAT surveys not sent for the week of 7/28 –
Started Aug 03, 2026, 05:00 PM UTC· resolved Aug 03, 2026, 05:00 PM UTC
- resolved Aug 07, 2026, 11:57 AM UTC
We identified an issue with CSAT surveys not going out for the mentioned week. We identified the issue and have fixed it; subsequent CSAT's should run as usual. We sincerely apologise for the inconvenience caused.
Minor July 29, 2026 Connector Credential Expiry False Alerts 7d 3h Connectors
Started Jul 29, 2026, 06:26 PM UTC· resolved Aug 05, 2026, 10:15 PM UTC
- investigating Jul 29, 2026, 06:26 PM UTC
We are investigating reports of false alerts regarding connector credential expiry across multiple customer instances. What's happening: Some customers are receiving notifications that their connector credentials have expired or are invalid. Our investigation confirms that affected connectors are functioning normally and successfully authenticating. Impact: No service impact. All connectors are functioning normally and authenticating successfully. The alerts being triggered are false positives due to an ongoing backend issue. What we're doing: Our engineering team is actively investigating and working on a resolution. What you should do: If you see a connector credential expiry alert, please make an API call using the connector in API Playground to validate your credentials. If you receive a successful response, your connector credentials are working fine and no action is required. We'll notify you when this is fully resolved. We apologize for the confusion. Thank you for your patience.
- resolved Aug 05, 2026, 10:15 PM UTC
This incident has been resolved.
Minor July 7, 2026 Moveworks Setup — Logs Delayed or Not Loading 38m Moveworks Setup
Started Jul 07, 2026, 03:39 PM UTC· resolved Jul 07, 2026, 04:17 PM UTC
- investigating Jul 07, 2026, 03:39 PM UTC
We're aware of an issue affecting Moveworks Setup where logs are currently not loading, and our team is actively investigating. We apologize for the inconvenience. Impacted Region: US
- resolved Jul 07, 2026, 04:17 PM UTC
Our engineering team has resolved the issue. Logs in Moveworks Setup are now loading as expected. Thank you for your patience, and apologies again for the inconvenience.
Minor June 26, 2026 Agent Studio — Compound Action Testing Failing 1h 54m Plugins Workspace
Started Jun 26, 2026, 06:09 PM UTC· resolved Jun 26, 2026, 08:03 PM UTC
- identified Jun 26, 2026, 06:09 PM UTC
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.
- monitoring Jun 26, 2026, 06:29 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 26, 2026, 08:03 PM UTC
This incident has been resolved
Major June 23, 2026 Permissions ingestion failing for Unily 50d 5h Enterprise Search, Connectors
Started Jun 23, 2026, 09:15 AM UTC· resolved Aug 12, 2026, 02:38 PM UTC
- identified Jun 23, 2026, 09:15 AM UTC
Permissions ingestion has been failing for Unily connectors. This is due to Unily deprecating their Permissions API, we are working with them to find a way forward. We will keep you posted on the progress. Until then, the newly added or updated permissions won't be ingested. We sincerely apologise for the inconvenience caused.
- identified Jun 23, 2026, 05:52 PM UTC
Unily has confirmed a fix is being packaged. Once it's available, customers will need to upgrade to the patched version. We encourage impacted customers to reach out to Unily directly, and we'll share more details as we have them.
- resolved Aug 12, 2026, 02:38 PM UTC
This incident has been resolved.
Minor June 22, 2026 Potential Search Retrieval Degradation 23h 36m Enterprise Search
Started Jun 22, 2026, 05:15 PM UTC· resolved Jun 23, 2026, 04:51 PM UTC
- identified Jun 22, 2026, 05:15 PM UTC
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.
- monitoring Jun 22, 2026, 06:59 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jun 23, 2026, 09:49 AM UTC
The fix has been rolled out to the majority of the affected customers; others will get the fix too shortly. We will keep you updated on the progress.
- resolved Jun 23, 2026, 04:51 PM UTC
The fix has been rolled out for all impacted customers and this incident has been resolved.
Minor June 18, 2026 Jira ITSM – Intermittent Update and Resolution Failures 7h 33m Concierge
Started Jun 18, 2026, 12:57 PM UTC· resolved Jun 18, 2026, 08:31 PM UTC
- identified Jun 18, 2026, 12:57 PM UTC
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.
- identified Jun 18, 2026, 12:58 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Jun 18, 2026, 03:21 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 18, 2026, 08:31 PM UTC
This incident has been resolved.
Major June 11, 2026 Enterprise Search Unavailable in AI Assistant — Resolved 1h 54m
Started Jun 11, 2026, 12:30 AM UTC· resolved Jun 11, 2026, 02:24 AM UTC
- resolved Jun 11, 2026, 02:31 AM UTC
On June 10, 2026, between 5:15 PM and 6:24 PM PST, users in the US region experienced a loss of Enterprise Search within the AI Assistant. Our team identified and resolved the issue within the same hour. We apologize for the impact to your experience.
Critical June 9, 2026 MyMoveworks Access Issue 1h 48m Moveworks Setup, Moveworks Documentation, Support, Community
Started Jun 09, 2026, 01:03 PM UTC· resolved Jun 09, 2026, 02:52 PM UTC
- investigating Jun 09, 2026, 01:03 PM UTC
We are currently investigating an issue that is preventing users from accessing the My Moveworks Portal. Our team is actively working to identify the root cause and restore full functionality as quickly as possible. We apologize for the inconvenience and will provide updates as our investigation progresses.
- identified Jun 09, 2026, 01:27 PM UTC
We have identified the issue and are currently working on deploying a fix. We will provide another update once the fix has been applied.
- monitoring Jun 09, 2026, 01:34 PM UTC
We have successfully applied a fix and confirmed that the My Moveworks Portal is loading as expected. We will continue to monitor to ensure full stability is maintained. Thank you for your patience.
- resolved Jun 09, 2026, 02:52 PM UTC
This incident has been resolved as of 6:30 AM PST. We apologize for any inconvenience this may have caused.
Minor June 5, 2026 AI Assistant Answers Degradation 1h 51m Enterprise Search
Started Jun 05, 2026, 01:08 PM UTC· resolved Jun 05, 2026, 02:59 PM UTC
- investigating Jun 05, 2026, 01:08 PM UTC
We are currently investigating an issue where the assistant is not serving answers from knowledge articles. We will provide updates as the investigation progresses.
- identified Jun 05, 2026, 01:32 PM UTC
We are seeing some improvement, but failures are still occurring. We are actively working on a fix and will continue to provide updates.
- monitoring Jun 05, 2026, 02:26 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 05, 2026, 02:59 PM UTC
This incident has been resolved.
Minor May 29, 2026 The line breaks and bolding of the words not being respected in the messages. –
Started May 29, 2026, 07:00 AM UTC· resolved May 29, 2026, 07:00 AM UTC
- resolved May 29, 2026, 12:38 PM UTC
The line breaks and bolding of the words were not being respected in the messages the Assistant was sending out, mainly the Employee Comms, Agent Studio messages.