Eptura Workplace experienced a minor incident on May 4, 2023 affecting System Status and Insights Module, lasting 1d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 04, 2023, 04:22 PM UTC
We are currently investigating this issue.
- investigating May 04, 2023, 06:29 PM UTC
We are continuing to investigate this issue. We appreciate your patience as we work towards a resolution.
- identified May 04, 2023, 07:07 PM UTC
The issue has been identified and a fix is being implemented.
- identified May 04, 2023, 09:24 PM UTC
The issue with All Users are marked as Remote has been identified and our team continues to work on a fix.
- identified May 05, 2023, 12:14 AM UTC
We are continuing to work on a fix for this issue.
- identified May 05, 2023, 12:34 PM UTC
We are continuing to work on a fix for this issue.
- monitoring May 05, 2023, 12:43 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 05, 2023, 04:24 PM UTC
This incident has been resolved.
- postmortem May 12, 2023, 07:35 PM UTC
**iOFFICE Detailed Root Cause Analysis – Severity 2 – 05/04/2023** **All User Profiles are Marked as Remote** **Description:** On May 4, 2023, at approximately 10:23am MST, multiple customers reported issues of the iOffice platform where all users are marked as remote. When trying to update user profile, an error was presented, “Could not get split”. The engineering team was able to identify the issue and released a fix for all customers. **Type of Event:** Performance Degradation **Services\\Modules Impacted:** Production **Timeline:** On May 4, 2023, at approximately 10:23am MST, multiple customers reported issues in iOffice where all users were marked as remote users. When trying to update their user profile, an error was presented, _could not get split_. At 1:04pm MST, the engineering team had identified the issue. Shortly after, customers were notified, and the Status Page was updated from Investigation to an Identified phase. At approximately 10:25pm, the fix was fixed and implemented. On May 5, 2023, the Status Page was updated from Identified to a Monitoring phase at 6:43am MST. As no additional customers reported this issue the Status Page was updated from Monitoring to Resolved. **Total Duration of Event:** 12HRS 2MINS **Root Cause Analysis:** The engineering team identified the Root Cause in the program and a minor code fix was implemented to correct it. **Preventative Action:** The issue was identified before the new iOffice product release on 05/26/2023. The preventative action is for product and engineering to revisit any known issues during a release and fix or remove the underlying issues that can cause problems after a new product release.