Is Moveworks Down Right Now? Check if there is a current outage ongoing.

We have identified an issue affecting JIRA customers, where users may receive intermittent failure messages from the AI Assistant. These failures occur when the AI Assistant encounters a problem while attempting to fetch a ticket from JIRA. This issue could impact multiple features, including software access, concierge, channel resolver, and account access. Currently, the issue appears to be external, but our team is actively working to mitigate its impact from our end. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will keep you updated as we make progress.

We have identified an issue where users are currently unable to use the "Brief Me" feature in AI Assistant. Our team is actively investigating the problem and will keep you updated as we make progress. We appreciate your patience and understanding during this time.

We have identified an issue where users are unable to access the Support Portal via My Moveworks. Our team is actively investigating the issue, and we sincerely apologize for any inconvenience this may cause. In the meantime, please feel free to send your queries to support@moveworks.ai. Thank you for your patience and understanding.

We're currently investigating an issue affecting the Channel Resolver Ticket Syncing feature. Comments added in Jira tickets are not syncing to the corresponding Slack threads. However, syncing from Slack to Jira remains fully functional. This issue is limited to Jira Cloud and does not impact Jira Server users. Our team is actively investigating the issue and will share updates as soon as possible.

We recently experienced an issue affecting the Moveworks AI Assistant due to performance degradation from a third party LLM provider. This led to a temporary decline in response quality, with responses sometimes generated based on outdated context or unrelated resources.The issue was characterized by reduced reasoning capability when selecting the appropriate context for user facing interactions. We are pleased to inform you that the issue has been resolved, and the Moveworks AI Assistant is now functioning normally. We apologize for any inconvenience this may have caused and appreciate your patience and understanding. Thank you for your continued support. Duration: 5/28/2025 1:27 PM PST - 5/29/2025 6:50 PM PST Regions: US

We recently experienced an issue affecting the Moveworks AI Assistant due to performance degradation from a third party LLM provider. This led to a temporary decline in response quality, with responses sometimes generated based on outdated context or unrelated resources.The issue was characterized by reduced reasoning capability when selecting the appropriate context for user facing interactions. We are pleased to inform you that the issue has been resolved, and the Moveworks AI Assistant is now functioning normally. We apologize for any inconvenience this may have caused and appreciate your patience and understanding.Thank you for your continued support.Duration: 5/28/2025 1:27 PM PST - 5/29/2025 6:50 PM PSTRegions: US

We have worked closely with Microsoft Teams to resolve the issue, and an update has been rolled out to fix it. All employees need to update their Moveworks AI Assistant application. A banner with an "Update" button will appear in the AI Assistant app for easy updating. We apologize for any inconvenience caused and appreciate your understanding. For more details, please refer to our community post here - https://community.moveworks.com/ai-assistant-78/microsoft-teams-customers-an-app-update-is-needed-2268

Please note that we are actively working with Microsoft to make the necessary updates to the App Store version of the Teams app. Moveworks customers using a custom (non app store) version of the Teams app will be able to update the manifest themselves. Customers can determine whether they are using an App Store version by following these steps: 1. Go to Moveworks Setup. 2. Navigate to Manage Chatbots. 3. Find the entry for the Teams bot and click Edit. 4. Scroll down to the "Microsoft Teams App Id" field. 5. If the App ID is b8ec4e1a-e05a-49d0-ba3a-05119b8b62c0, you are using the App Store bot. If the App ID is anything else, you are using a custom (non app store) version of the app and will need to update the manifest.json file to include "supportsFiles": true and upload it according to the instructions provided in the guide here - https://help.moveworks.com/docs/microsoft-teams-bot-non-app-store-setup-guide.

We have identified an issue where Microsoft Teams customers are unable to upload files via the Moveworks AI Assistant, preventing the use of the Brief Me (Limited Preview) feature and degrading the Message Brokering and Ticketing Capabilities. There is a manifest.json file that outlines the scopes of our Moveworks AI Assistant within Microsoft Teams. Historically, the "supportsFiles": false setting in the manifest.json file, which outlines the scopes of our Moveworks AI Assistant within Microsoft Teams, was not enforced by Microsoft, allowing file uploads to occur. We have got confirmation that Microsoft made a change this week to now require this field to be set to ‘true’ in the manifest.json file, causing the file upload capability to fail. If you are impacted by this issue, please work with your account team to update the manifest file to resolve the issue. We apologize for any inconvenience this may cause and appreciate your understanding and cooperation.

We have worked closely with Microsoft Teams to resolve the issue, and an update has been rolled out to fix it. All employees need to update their Moveworks AI Assistant application. A banner with an "Update" button will appear in the AI Assistant app for easy updating. We apologize for any inconvenience caused and appreciate your understanding. For more details, please refer to our community post here - https://community.moveworks.com/ai-assistant-78/microsoft-teams-customers-an-app-update-is-needed-2268

Please note that we are actively working with Microsoft to make the necessary updates to the App Store version of the Teams app. Moveworks customers using a custom (non app store) version of the Teams app will be able to update the manifest themselves. Customers can determine whether they are using an App Store version by following these steps:1. Go to Moveworks Setup.2. Navigate to Manage Chatbots.3. Find the entry for the Teams bot and click Edit.4. Scroll down to the "Microsoft Teams App Id" field.5. If the App ID is b8ec4e1a-e05a-49d0-ba3a-05119b8b62c0, you are using the App Store bot. If the App ID is anything else, you are using a custom (non app store) version of the app and will need to update the manifest.json file to include "supportsFiles": true and upload it according to the instructions provided in the guide here - https://help.moveworks.com/docs/microsoft-teams-bot-non-app-store-setup-guide.

We have identified an issue where Microsoft Teams customers are unable to upload files via the Moveworks AI Assistant, preventing the use of the Brief Me (Limited Preview) feature and degrading the Message Brokering and Ticketing Capabilities. There is a manifest.json file that outlines the scopes of our Moveworks AI Assistant within Microsoft Teams. Historically, the "supportsFiles": false setting in the manifest.json file, which outlines the scopes of our Moveworks AI Assistant within Microsoft Teams, was not enforced by Microsoft, allowing file uploads to occur. We have got confirmation that Microsoft made a change this week to now require this field to be set to ‘true’ in the manifest.json file, causing the file upload capability to fail.If you are impacted by this issue, please work with your account team to update the manifest file to resolve the issue. We apologize for any inconvenience this may cause and appreciate your understanding and cooperation.

This incident has been resolved. Events Triggered Paths are functioning as usual as of 10:11 AM PT.

We are currently aware of an issue where the Events Triggered Paths in Agent Studio – Classic (Creator Studio) are not functioning as expected. Our team has identified the root cause and is actively working on a resolution. We appreciate your patience and will keep you informed with regular updates as we progress toward a fix. We sincerely apologise for any inconvenience this may have caused.

The incident has been resolved. We apologise for any inconvenience this may have caused.

We've currently identified an issue where the AI Assistant Insights Overview is not displaying any user interaction data for US region users. Our engineering team has identified the root cause and is actively developing a fix. We appreciate your patience and will continue to provide updates as progress is made.

Slack has confirmed that the issue impacting their services has now been resolved. Users should no longer experience difficulties accessing the AI assistant via Slack, and all functionalities should be operating normally. We appreciate your patience and understanding during this time.

We want to inform you that there is a current outage affecting Slack, which may impact your ability to access the AI assistant through the Slack platform. According to Slack's status update, users are experiencing issues connecting to Slack, including difficulties loading threads and sending messages, due to backend database routing issues causing error spikes across many Slack features. This may result in difficulties booting the Slack client and messages to and from the AI assistant failing to send. Slack is actively working to identify and resolve the routing issues and is closely monitoring error rates. For more details on the Slack outage, please refer to their status page: https://slack-status.com/2025-05/7b32241eb41a54aa We appreciate your patience and understanding as Slack works to resolve these issues, and we will continue to monitor the situation and provide updates as necessary.

We experienced an issue on April 29th from 3:10 AM PST to 1:40 PM PST, which affected AI Assistant's ability to process and understand Entities accurately. As a result, requests to our services that analyze entity information may not have functioned correctly during this time. We understand that this could have affected the quality of interactions and ticket routing. We have resolved the issue by restoring the correct data, and we are implementing measures to prevent a recurrence. We apologize for any inconvenience this may have caused and appreciate your patience and understanding.

The issue has been fully resolved, and the ticket interception plugin has been reenabled and is functioning as expected. We appreciate your patience and understanding during this time.

Our engineering team has identified the root cause and developed a fix for the issue affecting the Ticket Interception plugin. The fix is currently undergoing final validation, and we remain on track to restore the plugin’s functionality by the end of the day. We appreciate your patience as we work to resolve this.

As of May 2, 2025, we have temporarily disabled the Ticket Interception plugin for all customers using the AI Assistant. This action was taken after identifying an issue where the AI Assistant may post comments on tickets—such as “User said they are still having issues”—even though no outreach was made via the plugin. Disabling the plugin prevents further erroneous behavior while we work on a resolution. Our engineering team has identified the root cause and is actively developing a fix. Testing and deployment are currently underway, and we’re aiming to release the update by the end of the day, assuming no unexpected issues arise. We appreciate your patience and will continue to provide updates as progress is made.

A fix was deployed at 11:57am PT, and monitoring has indicated the degradation has been resolved.

We have identified an issue that is causing degraded performance in bot recognition of common entities in user utterances and tickets. The issue may degrade performance of Software Access and Employee Experience Insights. Our team has identified the issue and a fix is being implemented. We appreciate your patience and understanding as we work towards a swift resolution.

Some customers will find that AI Assistant Analytics Report data may be missing from April 21st, between 5 AM and 6 PM UTC. We deeply regret any inconvenience this may cause.

We have identified the issue causing delays in the AI Assistant Analytics reports and have implemented a fix. We are actively monitoring the situation to ensure everything is functioning smoothly. We appreciate your patience and understanding. We will provide an update with the new estimated time of availability as soon as possible.

There will be a delay in today's AI Assistant Analytics reports due to unforeseen circumstances. We apologize for any inconvenience caused due to this delay. We will provide an update once the new ETA is available.

We have identified and addressed an issue where some users might have received the error message, "Looks like I am having some trouble responding to you right now" while interacting with the AI Assistant. We sincerely apologize for any inconvenience this may have caused. The issue has been resolved. Our team is actively reviewing the incident to prevent similar issues in the future. We appreciate your patience and understanding during this time. If you continue to experience any issues, please reach out to our support team. Thank you for your understanding. Affected Regions: US Timeline: Start Time: 5:25 PM PST End Time: 6:47 PM PST

We experienced an issue affecting all Moveworks AI assistant capabilities, causing temporary failures for some users. We sincerely apologize for any inconvenience caused due to this issue. Affected Regions: US , Canada Timeline: Start Time: April 15, 2025, 2:08 PM PST Resolved Time: April 15, 2025, 3:26 PM PST

This incident has been resolved.

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

We have identified an issue where some users are receiving the error message: "Looks like I am having some trouble responding to you now. Please try again later - usually, I bounce back quickly" when interacting with specific buttons served by the AI Assistant. This issue specifically affects any Creator Studio Path containing multiple choice type slots with the "explicit questions" feature enabled. Our team has located the root cause of this problem and is actively working on a fix. We apologize for any inconvenience this may cause and appreciate your patience. Further updates will be provided as we make progress.

This incident has been resolved as of 7:20 PM PST.

We have identified an ongoing failure with the knowledge ingestion process. As a result, updates or new knowledge articles published since 3/24 approximately 11 AM PST may not be reflected in your AI Assistant. Our team is working diligently to resolve this issue and appreciates your patience as we work through this.

This incident has been resolved.

We have implemented a fix to mitigate the impact of the change and are currently monitoring the results.

We've learned that customers using JIRA service desk are experiencing failures while performing ticketing related actions including triage. Upon investigation, we have confirmed that these issues are related to a recent update in JIRA, where API calls with a body are being rejected by AWS CloudFront. You can find more details on the Atlassian community page here - https://community.atlassian.com/forums/Atlassian-Platform-articles/Jira-Confluence-Cloud-APIs-return-403-Error-The-request-could/ba-p/2928153. Our engineering team is actively working on implementing a fix to mitigate the impact of this change. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding.

Moveworks AI Assistant is now consistently responding to requests on Slack as expected.

Based on the latest update from Slack, the issues affecting the Moveworks AI Assistant on Slack should be mostly resolved. We are currently monitoring for any additional issues. For more details, please refer to the Slack incident report: https://slack-status.com/2025-02/d41e4bfd1ccae26a

We are continuing to experience an issue where the Moveworks AI Assistant is not responding to users as expected on Slack. Slack has identified the root cause and is actively working on resolving the issue. As detailed in Slack's Incident report, Slack has begun re-processing a backend job and once it is complete, new requests should begin to work as expected. Slack has communicated the expectation that it will take a couple of hours. We appreciate your patience as we await further updates. We will provide new information as it becomes available and confirm once the issue is fully resolved.

We have identified an issue where the Moveworks AI Assistant is not responding to users as expected. Slack has acknowledged that the root cause is on their end and has begun investigating. For more details, please refer to the Slack incident report: https://slack-status.com/2025-02/d41e4bfd1ccae26a We apologize for any inconvenience and appreciate your patience as we await further updates.

Slack has confirmed the restoration of full functionality to all affected features, including messages and other API-related services that were impacting the Moveworks AI Assistant on Slack. If you're still experiencing any issues, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). For more details, please visit: https://slack-status.com/2025-02-26 Thank you for your patience.

Please refer slack status page (https://slack-status.com/2025-02-26) for latest updates

We've received reports that customers using Slack are experiencing delays in receiving responses from the Moveworks AI Assistant. The issue appears to be related to Slack and is currently under investigation. For more details and updates, please visit: https://slack-status.com/2025-02-26 We apologize for any inconvenience this may cause and appreciate your patience as we work towards a resolution.

This incident has been resolved.

We are actively investigating an issue where some users are not receiving event notifications. We apologize for the inconvenience this may cause and will keep you posted on our findings.

This incident has been resolved.

We are aware of an issue in Microsoft Teams affecting the formatting of link citations and feedback/help options in the bot. Microsoft has identified the issue and has confirmed that a fix is scheduled to roll out in the next release scheduled for the 4th week of January. For ongoing updates, you can track the status of this issue in the Service Health section of the Microsoft 365 Admin Center under issue TM962326. We apologize for any inconvenience and appreciate your understanding as Microsoft works to resolve this.

We have received confirmation from Microsoft Azure support that this incident was resolved as of 4:30 AM PST.

We have identified an issue where Copilot is failing for some users with the error message: "Sorry, this request is taking much longer than normal. I'll be available again shortly. Thanks." This is due to degradation in the Microsoft Azure OpenAI endpoints. Users may experience intermittent failures and delays when using Copilot. Our team is actively monitoring the situation and are working with our partners at Microsoft to expedite the resolution. We sincerely apologize for any inconvenience caused by this issue and appreciate your patience and understanding.

We have identified and resolved an issue where Google Drive integrations were failing, resulting in the unavailability of Google Drive files via the bot. We sincerely apologize for any inconvenience caused due to this issue and appreciate your patience and understanding. If you have any further questions or continue to experience issues, please contact our support team. Duration: 1/15/2025 1:39 PM PST - 1/22/2025 1:35 PM PST

This incident has been resolved.

We have identified an issue that is impacting customers who have set up Ariba approvals via the bot. Our team has initiated a fix and we expect to resolve this issue soon. We apologize for the inconvenience caused and appreciate your patience as we work to address this issue. Thank you for your understanding.

The incident has been resolved as of 11:15AM PST. We appreciate your patience and understanding.

We have identified an issue that is causing certain use cases in Creator Studio to fail, specifically subsequent actions within paths are impacted. Our engineering team has applied a fix and is currently monitoring the results to ensure it is fully resolved. We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we work to restore full functionality. Thank you for your understanding.

We have identified and resolved an issue that resulted in the dropping of Creator Studio logs between 1/2/2025 11:00 AM PST and 1/3/2025 1:40 PM PST. We sincerely apologize for any inconvenience this may have caused.

We have identified and resolved an issue that was impacting create or update actions within My Moveworks Portal, including Creator Studio and Moveworks Setup changes. Additionally, this outage affected the Creator Studio logging feature during that period. We sincerely apologize for any inconvenience this may have caused. Start Time: 1/2/2025 11:00 AM PST Resolution Time: 1/2/2025 4:40 PM PST Thank you for your understanding and patience.

At 5:55 PM PST we observed that the degradation was no longer apparent. The partial outage is resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor the updates from OpenAI. As of 6:36 PM PST, OpenAI's service is partially recovered.

We are continuing to investigate this issue.

We've detected an issue causing some users in our US, Canada and Australia datacenters to experience degraded performance in Copilot, stemming from the current OpenAI outage https://status.openai.com/incidents/ctrsv3lwd797 We sincerely apologize for any inconvenience this may cause and appreciate your understanding.

This incident has been resolved as of 1 PM PST.

We are investigating an issue where the events API messages are getting delivered but not returning a successful response and often returning an error " Error while copying content to a stream". We are actively working on addressing the issue and sincerely apologize for any inconvenience caused.

This incident has been resolved, and the User Insights feature in Copilot Insights will be made available by 10th Dec 2024. Please feel free to refer to the community post here https://community.moveworks.com/analytics-89/introducing-user-insights-in-copilot-analytics-1755?tid=1755&fid=89 for details.

We have rolled back the User Insights feature in Copilot Insights as part of the maintenance and will be reintroducing the feature at a later date. We sincerely apologize for any inconvenience caused. Please feel free to refer the community post here https://community.moveworks.com/analytics-89/introducing-user-insights-in-copilot-analytics-1755?tid=1755&fid=89 for details.

we have identified an issue where some customers are unable to access User Insights dashboard within Copilot Insights. This issue is not impacting customers who have deployed Copilot in chat platforms like Microsoft teams or Slack.

This incident has been resolved. Duration: 16:08 PST - 17:49 PST Impacted Regions: US, CA and AU

As per the latest update from OpenAI the issue has been mitigated as of 17:49 PST. They are currently monitoring for any further issues. Duration: 16:08 PST - 17:49 PST Impacted Regions: US, CA and AU.

We've detected an issue causing some users to experience degraded performance in Copilot, stemming from the current OpenAI outage https://status.openai.com/incidents/55qs3vq1m35z. We sincerely apologize for any inconvenience this may cause and appreciate your understanding.

The root cause was an assumption made in the guardrails used by Moveworks Copilot Channel Resolver to prevent reaching out to users with answers that are not grounded in customer knowledge content and automations. On November 4, 2024, we launched [multi-plugin response](https://community.moveworks.com/moveworks-copilot-78/upcoming-copilot-will-now-summarize-multiple-plugin-responses-1546?tid=1546&fid=78), a feature that allows Moveworks Copilot to call multiple plugins in parallel and integrate the responses into a single answer. Multi-plugin response introduced a new plugin response behavior pattern that occasionally broke the assumption above made by Channel Resolver guardrails. The decrease in reachouts was corrected by deploying an update to the guardrails.

We would like to inform you that we have identified and resolved a recent issue affecting Channel Resolver in Moveworks Copilot. Moveworks Copilot was reaching out with resolutions to posts in channels for which Channel Resolver is enabled 10-20% less often than expected. This decrease led to missed opportunities to help customer employees with issues for which relevant resources to answer the query were available. Fixes were deployed to all customers between November 22 and November 25.

We've identified and resolved an issue that was affecting URL links and buttons within employee communications platform. Prior to the fix, users experienced errors on the UI when attempting to click on or expand these links and buttons. The issue has been resolved and we can now confirm that all URL links and buttons within the employee comms should be functioning as expected. We sincerely apologize for any inconvenience this may have caused. Thanks for your understanding

We would like to inform you that we have identified and resolved a recent issue affecting the Creator Studio. Some of the creator studio users experienced difficulties in viewing use cases within the Creator Studio. We understand the inconvenience this may have caused and sincerely apologize for any disruption to your work.

We've identified and addressed an issue where Copilot's disclaimer message wasn't showing in chat and pop up pages. We sincerely apologize for any inconvenience caused due to this issue. Duration: 10/18/2024 1:02 PM PST - 2:40 PM PST

This incident has been resolved as of 11:28AM PST.

We've identified an issue where some users are encountering failures while trying to update API action within their paths use cases. We apologize for any inconvenience this may have caused. We are committed to providing you with updates as they become available and will notify you as soon as the issue has been resolved.

Our team has successfully identified and resolved an issue where some users were unable to get the query triggered path use cases functioning as expected. We understand the inconvenience this may have caused and sincerely apologize for any disruption to your work.

This incident has been resolved.

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

We are actively working on implementing a fix. We appreciate your patience during this process.

We have identified an issue where some users are experiencing failures when executing certain paths use cases that involves submission of a form. We have identified a solution and are actively working to implement the fix. We sincerely apologize for any inconvenience this issue may have caused.

We would like to inform you that we identified and resolved an issue affecting Moveworks for Web. During this outage, users might have experienced difficulties in interacting with the Moveworks for Web bot. We sincerely apologize for any inconvenience this may have caused you. Duration: September 13, 4:30 AM - 5:45 AM PST

Microsoft has confirmed the fix is fully deployed and the avatar icon issue is resolved.

Microsoft Teams' fix deployment has been delayed past the initial 8/22 ETA. Please refer to the published Microsoft ICM and communication for more details on when the fix will be available.

Microsoft has informed us that the fix is being rolled out and should be available by Aug 22.

Some users may see a default icon in the Microsoft Teams Web app and the New Desktop client instead of the expected Bot Avatar, however, the bot will continue to function as expected. Microsoft has identified a recent feature release that was not fully implemented into the service. They've included that feature in the upcoming deployment which they expect will alleviate impact. The Teams deployment is expected to alleviate impact on August 5th, 2024. For more details, Teams administrators can review the Microsoft Service Health Issue Advisory TM810917 in the Microsoft 365 Admin Center.

The issue with Copilot action receipts not being received has been fixed as of 1 PM PST. We appreciate your patience while we resolved this.

We have identified an issue that is causing degraded performance in Copilot actions. Our team is actively investigating the matter to promptly resolve the issue. We appreciate your patience and understanding as we work towards a swift resolution.

We have identified that the root cause of the issue is a permissions shortfall, notably the missing "Send Reply to a Ticket" permission under "View Tickets" for the Moveworks Admin role within Freshservice. Should you be experiencing this problem, we encourage you to consult our Freshservice Access Requirements documentation at https://help.moveworks.com/docs/freshservice-access-requirements#create-custom-moveworks-admin-role for guidance on updating the necessary permissions. Furthermore, for those affected by this issue, your Customer Success team will proactively contact you with detailed resolution steps. If you require further assistance, please do not hesitate to get in touch with our support team.

We have verified that the issue specifically affects Freshservice integrations, occurring while performing ticketing operations via the bot that involve the addition of public comments. We appreciate your patience as we continue to investigate the issue.

We have identified an issue affecting our Freshservice customers, who are experiencing difficulties with ticketing operations through the bot. We apologize for any inconvenience this may cause and want to assure you that we are actively working to resolve the issue.

This incident has been resolved.

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

We have identified an issue that is causing failures when attempting to make modifications within the Creator Studio and Moveworks Setup Configurations. We sincerely apologize for any inconvenience this may cause and want to assure you that we are actively working to resolve the issue as quickly as possible.

We identified an issue with Creator Studio Queries that was causing some query APIs to not be executed between approximately 3:00 PM and 5:30 PM PT. We apologize for any inconvenience this caused. This issue is now resolved.

This issue is resolved as of 1:35PM PST. We appreciate your patience and understanding as we worked to get this resolved and apologize for any inconveniences caused.

We've identified a solution and are currently in the process of deploying the fix. We appreciate your continued patience and understanding during this time.

We've identified an issue affecting the functionality of our handoff buttons within MS Teams. Currently, users may find they are unable to trigger modal pop ups through any of the handoff options in Copilot, with the exception of the "File Ticket" option. We sincerely apologize for any inconvenience this issue may have caused. Rest assured, we will provide you with updates on the progress of the fix.

We are pleased to inform you that this incident has been resolved. Users should now be able to look up tickets as expected. Should you encounter any further issues, we recommend trying a few different queries before attempting to look up the ticket again. Your experience is important to us, and we appreciate your patience and understanding during this time. If the problem persists or you need further assistance, please do not hesitate to reach out to our support team.

We are currently investigating an issue where some users may experience difficulties in looking up tickets within Copilot. Rest assured, our team is working diligently to identify and resolve this problem as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience while we work towards a solution

This incident has been successfully resolved. The MFA reset functionality should now be working correctly within the classic bot experience.

In the classic bot experience, users who request a MFA reset will get the proper response "Ok, I understand you are having issues with your Multi-Factor Authentication (MFA). I can help!" "Would you like me to reset your MFA?" however they do not have a "Yes" option and are not able to proceed with the MFA reset. We've identified the cause of the issue and our team is working diligently to get this issue resolved as soon as possible. We appreciate you patience as we get this corrected.

This incident has been resolved.

We're still in the process of rolling out the fix. Appreciate your continued patience.

We've identified a solution for the issue and are currently in the process of implementing the fix. We appreciate your continued patience as we work to resolve this issue.

We're currently investigating an issue impacting form ingestion from ServiceNow. Due to this issue, the most recent updates to ServiceNow forms might not be reflected in the bot. Our team has identified the root cause and is actively working towards a resolution. We value your patience and understanding while we address this matter. Please stay tuned for upcoming updates.

This incident has been resolved.

We have identified an issue where some users are unable to access the bot. We apologize for the inconvenience and will keep you updated on our progress.

We're pleased to inform you that the incident has been resolved. All users should now be receiving ticket notifications without issue. Thank you for your patience while we worked to address this matter.

We're currently addressing an issue where some users may not be receiving ticket notifications as expected. We apologize for any inconvenience this may cause and appreciate your patience as we work to resolve the matter promptly.

We are pleased to inform you that the Microsoft team has successfully implemented a fix to address this issue. We appreciate your patience and understanding while we worked closely with Microsoft towards a resolution. Should you have any further questions or require additional assistance, please do not hesitate to reach out to our support team.

We are currently investigating reports of an issue affecting some users when clicking buttons that open a pop-up window within the Moveworks bot on Microsoft Teams. Users encountering this problem may see an error message stating, "There was a problem reaching this app." At this time, it appears that not all users and/or organizations are impacted, suggesting a selective occurrence. We want to reassure our users that we are actively collecting details and have shared our findings with Microsoft for further investigation. In the meantime, we recommend that affected organizations file a support ticket directly with Microsoft to expedite resolution. We apologize for any inconvenience caused and appreciate your patience as we work toward a solution. We will continue to provide updates as we gather more information. Thank you for your understanding.

We've reported the issue to Microsoft who has been able to identify and resolve the issue. For more details on the issue, please reach out to Microsoft.

We're investigating an intermittent issue affecting traffic to and from users on Teams bots. Users may receive a "Sorry, this request is taking much longer than normal. I'll be available again shortly. Thanks" response from the bot if affected.

This issue has been reported to be resolved by the affected customers. If your organization is experiencing this issue please file a ticket with Microsoft Teams.

We've received reports of users not being able to interact with the bot on the Microsoft Teams platform. We've reported the issue to Microsoft and are working with them to help investigate the bot application permissions within Teams which appear to not be respected resulting in the bot appearing as disabled. At this time, the issue appears to only apply to bots configured as a custom app in Teams and does not appear to apply to bots configured via the Moveworks app in the Teams app store. We recommend advising users to clear the Teams cache to potentially resolve the issue: https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache