This incident has been resolved.
Between 16:00 and 16:06 WIB on 23 September 2026, workflow executions experienced significantly elevated response times. A high volume of custom list creation requests triggered a cache refresh routine that was far more resource intensive than necessary. Because the caching component is shared, the slowdown affected workflow executions beyond the list feature itself.
Resolution: We optimized the cache refresh mechanism. List creation is now substantially faster, and it no longer affects other operations.
Next steps: We are adding safeguards so that a single type of operation cannot degrade shared components, and we are improving alerting so we catch similar patterns sooner.
Resolved
This incident has been resolved.
Between 16:00 and 16:06 WIB on 23 September 2026, workflow executions experienced significantly elevated response times. A high volume of custom list creation requests triggered a cache refresh routine that was far more resource intensive than necessary. Because the caching component is shared, the slowdown affected workflow executions beyond the list feature itself.
Resolution: We optimized the cache refresh mechanism. List creation is now substantially faster, and it no longer affects other operations.
Next steps: We are adding safeguards so that a single type of operation cannot degrade shared components, and we are improving alerting so we catch similar patterns sooner.
Monitoring
We have identified the cause of the issue.
The affected component recovered at 16:06 WIB, and response times have returned to normal. We have deployed a fix that changes how the cache is refreshed when custom lists are created, so these requests no longer place broad load on the caching layer. We are monitoring closely to confirm stability.
Investigating
We are currently investigating a service issue.
Some customers may experience degraded performance, intermittent errors, or delays.
Our team is actively investigating and will provide an update as soon as we have more information.