Resolved -
We have identified a display issue within Microsoft Teams, following a recent MS Teams update, where some users may not see the Moveworks bot logo as expected. To address this, we recommend the following troubleshooting steps for individual users:
1. Ensure you are using the latest version of Microsoft Teams. 2. Quit Microsoft Teams and then relaunch the application. 3. Remove the Moveworks bot from your Teams and then add it back again from the apps section.
If the issue persists after trying these steps, please do not hesitate to contact the Moveworks support team for further assistance.
Apr 19, 16:00 UTC
Resolved -
We wanted to inform you that there will be a delay in today's daily insights data report due to unforeseen circumstances. We're extending the ETA to 10 PM PST. We apologize for any inconvenience caused due to this delay.
Apr 13, 02:00 UTC
Resolved -
This incident has been resolved.
Apr 11, 18:34 UTC
Investigating -
We are currently investigating an issue affecting My Moveworks, specifically within the EXI (Employee Experience Insights) and Analytics screens. Users may find themselves unable to perform downloads at this time.
Our team has identified the problem and is actively working on a solution. We understand the inconvenience this may cause and appreciate your patience and understanding.
Apr 11, 18:21 UTC
Resolved -
This incident has been resolved
Apr 10, 16:24 UTC
Monitoring -
A fix has been implemented and we are currently monitoring the results.
Apr 10, 15:31 UTC
Update -
After further investigation, we have confirmed that this issue is only impacting use cases that utilize the email address attribute. We are actively working on implementing a fix to resolve this issue. We will continue to keep you updated on our progress.
Apr 10, 14:33 UTC
Identified -
We have identified an issue affecting some use cases within Creator Studio, resulting in failures to execute as expected. Our team is actively investigating the matter to resolve it as swiftly as possible. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding as we work to rectify this issue.
Apr 10, 13:50 UTC