Resolved -
This incident has been resolved.
May 7, 05:54 PDT
Update -
We are continuing to monitor for any further issues.
May 7, 05:12 PDT
Update -
A fix has been implemented and we are monitoring the system.
May 7, 05:12 PDT
Monitoring -
A fix has been implemented and we are monitoring the results.
May 7, 05:09 PDT
Update -
Executions are running fine now. However, there is still some slowness in the execution graph generation so we might see some delay in the execution updates to show up in UI.
But executions would work without any delay/slowness.
May 7, 05:06 PDT
Identified -
We have identified the root cause as elevated queue depth and throughput saturation on the MongoDB layer, leading to processing latency. A fix is being implemented to optimize handling and restore database stability
May 7, 04:20 PDT
Update -
We are continuing to investigate this issue.
May 7, 03:19 PDT
Investigating -
We are currently investigating this issue.
May 7, 01:00 PDT