Contact Moveworks Support                                                                                                         
Update - 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.

Feb 25, 2025 - 23:45 UTC
Identified - 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.

Feb 21, 2025 - 01:32 UTC
Enterprise Messaging Integrations ? Operational
Microsoft Teams ? Operational
Moveworks for Web ? Operational
Cisco Webex Teams ? Operational
Google Chat ? Operational
Slack Messaging ? Operational
Slack Apps/Integrations/APIs ? Operational
Slack Notifications ? Operational
Slack Connections ? Operational
Access Skills Operational
Account Access ? Operational
Group Access ? Operational
Software Access ? Operational
Smart Forms ? Operational
Enterprise Approvals ? Operational
Answers ? Operational
Concierge ? Operational
Triage ? Operational
Lookups ? Operational
Employee Experience Insights Operational
Multilingual Support (MLS) Operational
Creator Studio Operational
Paths Workspace Operational
Queries Workspace Operational
Events Workspace Operational
Plugins Workspace Operational
Control Center Operational
Channel Resolver Operational
Performance Insights ? Operational
Moveworks AI Assistant ? Operational
AI Assistant Analytics Operational
Employee Communications ? Operational
My Moveworks Portal Operational
Moveworks Setup Operational
Moveworks Documentation ? Operational
Support ? Operational
Community ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Mar 29, 2025

No incidents reported today.

Mar 28, 2025

No incidents reported.

Mar 27, 2025
Resolved - This incident has been resolved as of 7:20 PM PST.
Mar 27, 04:57 UTC
Identified - 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.
Mar 26, 22:24 UTC
Mar 26, 2025
Mar 25, 2025

No incidents reported.

Mar 24, 2025

No incidents reported.

Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025

No incidents reported.

Mar 20, 2025

No incidents reported.

Mar 19, 2025

No incidents reported.

Mar 18, 2025
Resolved - This incident has been resolved.
Mar 18, 02:12 UTC
Monitoring - We have implemented a fix to mitigate the impact of the change and are currently monitoring the results.
Mar 11, 15:46 UTC
Identified - 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.

Mar 7, 14:18 UTC
Mar 17, 2025

No incidents reported.

Mar 16, 2025

No incidents reported.

Mar 15, 2025

No incidents reported.