Historial de interrupciones de Moveworks

1. 11 de agosto de 2026 a las 17:45 UTCmonitoring

   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.

2. 12 de agosto de 2026 a las 14:38 UTCresolved

   This incident has been resolved.

Traducido automáticamente desde la actualización oficial del incidente.

1. 10 de agosto de 2026 a las 13:41 UTCidentified

   We have identified authentication failures affecting SharePoint Online integrations that use Microsoft App Store authentication, following Microsoft’s deprecation of the legacy ACS authentication method. As a result, legacy SharePoint knowledge ingestion will fail for affected customers. As an immediate workaround, please follow the SharePoint Online Azure App Registration guide. https://docs.moveworks.com/service-management/access-requirements/knowledge-base-systems/sharepoint-online-access-requirements-new-1#1-configure-azure-app-registration Engineering is working on a JWT-based update for Microsoft App Store authentication. We will share additional updates as they become available.

1. 10 de agosto de 2026 a las 12:46 UTCinvestigating

   Nuestro sitio de documentación está actualmente desactivado; estamos trabajando con el proveedor para recuperarlo y correr. Sinceramente nos disculpamos por el inconveniente mientras tanto.

2. 10 de agosto de 2026 a las 12:53 UTCmonitoring

   The fix has been implemented, the site is loading fine now, and we are continuing to monitor it.

3. 10 de agosto de 2026 a las 17:33 UTCresolved

   This incident has been resolved.

Traducido automáticamente desde la actualización oficial del incidente.

1. 7 de agosto de 2026 a las 11:57 UTCresolved

   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.

1. 29 de julio de 2026 a las 18:26 UTCinvestigating

   Estamos investigando informes de falsas alertas sobre la caducidad credencial del conector en múltiples instancias del cliente. Lo que está sucediendo: Algunos clientes reciben notificaciones de que sus credenciales de conector han expirado o son inválidas. Nuestra investigación confirma que los conectores afectados funcionan normalmente y con éxito autenticando. Impacto: Sin impacto de servicio. Todos los conectores funcionan normalmente y se autentican con éxito. Las alertas que se desencadenan son falsos positivos debido a un problema de backend en curso. Lo que estamos haciendo: Nuestro equipo de ingeniería está investigando y trabajando activamente en una resolución. Lo que deberías hacer: Si ve una alerta de caducidad credencial del conector, por favor haga una llamada API usando el conector en API Playground para validar sus credenciales. Si recibe una respuesta exitosa, sus credenciales de conexión están funcionando bien y no se requiere ninguna acción. Te avisamos cuando esto esté completamente resuelto. Nos disculpamos por la confusión. Gracias por su paciencia.

2. 5 de agosto de 2026 a las 22:15 UTCresolved

   This incident has been resolved.

Traducido automáticamente desde la actualización oficial del incidente.

1. 7 de julio de 2026 a las 15:39 UTCinvestigating

   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

2. 7 de julio de 2026 a las 16:17 UTCresolved

   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.

1. 26 de junio de 2026 a las 18:09 UTCidentified

   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.

2. 26 de junio de 2026 a las 18:29 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 26 de junio de 2026 a las 20:03 UTCresolved

   This incident has been resolved

1. 23 de junio de 2026 a las 9:15 UTCidentified

   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.

2. 23 de junio de 2026 a las 17:52 UTCidentified

   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.

3. 12 de agosto de 2026 a las 14:38 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de junio de 2026 a las 17:15 UTCidentified

   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.

2. 22 de junio de 2026 a las 18:59 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 23 de junio de 2026 a las 9:49 UTCmonitoring

   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.

4. 23 de junio de 2026 a las 16:51 UTCresolved

   The fix has been rolled out for all impacted customers and this incident has been resolved.

1. 18 de junio de 2026 a las 12:57 UTCidentified

   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.

2. 18 de junio de 2026 a las 12:58 UTCidentified

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

3. 18 de junio de 2026 a las 15:21 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 18 de junio de 2026 a las 20:31 UTCresolved

   This incident has been resolved.

1. 11 de junio de 2026 a las 2:31 UTCresolved

   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.

1. 9 de junio de 2026 a las 13:03 UTCinvestigating

   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.

2. 9 de junio de 2026 a las 13:27 UTCidentified

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

3. 9 de junio de 2026 a las 13:34 UTCmonitoring

   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.

4. 9 de junio de 2026 a las 14:52 UTCresolved

   This incident has been resolved as of 6:30 AM PST. We apologize for any inconvenience this may have caused.

1. 5 de junio de 2026 a las 13:08 UTCinvestigating

   We are currently investigating an issue where the assistant is not serving answers from knowledge articles. We will provide updates as the investigation progresses.

2. 5 de junio de 2026 a las 13:32 UTCidentified

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

3. 5 de junio de 2026 a las 14:26 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 5 de junio de 2026 a las 14:59 UTCresolved

   This incident has been resolved.

1. 29 de mayo de 2026 a las 12:38 UTCresolved

   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.

1. 20 de mayo de 2026 a las 12:28 UTCidentified

   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.

2. 20 de mayo de 2026 a las 14:06 UTCresolved

   We are pleased to inform you that the issue with the View Permission feature in Setup has been resolved. The feature is now returning the expected results. We apologize for the inconvenience caused and thank you for your patience.

1. 19 de mayo de 2026 a las 16:42 UTCidentified

   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.

2. 19 de mayo de 2026 a las 17:51 UTCidentified

   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.

3. 19 de mayo de 2026 a las 20:06 UTCresolved

   This incident has been resolved. User Identity Ingestion is now functioning as expected and user identity sync has been restored for all affected customers. We apologize for any inconvenience this may have caused.

1. 12 de mayo de 2026 a las 20:35 UTCidentified

   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.

2. 12 de mayo de 2026 a las 20:55 UTCresolved

   This incident has been resolved as of 1:45 PM PST. Live Agent Chat has been restored and is functioning as expected. We appreciate your patience and apologize for any inconvenience caused.

1. 22 de abril de 2026 a las 16:43 UTCinvestigating

   We are actively investigating an issue where some users are not seeing the Moveworks Embedded AI Assistant loading on their employee service portals or intranet sites. We appreciate your patience and will provide updates as our investigation progresses.

2. 22 de abril de 2026 a las 17:07 UTCidentified

   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.

3. 22 de abril de 2026 a las 17:44 UTCresolved

   We are pleased to confirm that the issue causing the Moveworks AI Assistant to not load on web pages has been fully resolved. We appreciate your patience and apologize for any inconvenience this may have caused.

1. 24 de marzo de 2026 a las 16:45 UTCinvestigating

   We have identified an issue where users are currently unable to chat with the AI Assistant on Microsoft Teams. Our team is actively investigating the root cause and working to resolve this as quickly as possible. We appreciate your patience and will share updates as soon as more information becomes available.

2. 24 de marzo de 2026 a las 17:08 UTCinvestigating

   We currently suspect this may be related to a Microsoft Teams issue and are actively working with Microsoft to help drive resolution. We appreciate your patience and will share updates as soon as more information becomes available

3. 24 de marzo de 2026 a las 17:27 UTCidentified

   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

4. 24 de marzo de 2026 a las 17:55 UTCidentified

   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.

5. 24 de marzo de 2026 a las 18:34 UTCidentified

   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.

6. 24 de marzo de 2026 a las 19:02 UTCidentified

   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.

7. 24 de marzo de 2026 a las 19:42 UTCmonitoring

   Based on our recent testing, the AI Assistant on Microsoft Teams is now functioning as expected. We will continue to closely monitor the situation and provide further updates if needed. We appreciate your continued patience as the situation stabilizes.

8. 24 de marzo de 2026 a las 20:31 UTCresolved

   This incident has been resolved.

1. 18 de marzo de 2026 a las 16:40 UTCidentified

   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

2. 18 de marzo de 2026 a las 17:08 UTCidentified

   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.

3. 18 de marzo de 2026 a las 17:23 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 18 de marzo de 2026 a las 17:50 UTCresolved

   We’re pleased to confirm that the issue has been resolved. Thank you for your patience and continued support.