We want to share an update on a recent automation issue, including what happened, how it was resolved, and the steps we’ve taken to prevent it from happening again.
Between January 21 and January 23, 2026, some customers experienced delays in automated workflow execution. Automation workflows entered a “waiting” state and were processed behind schedule rather than in real time.
While no data was lost, workflow execution was slower than expected, which may have delayed downstream actions that depend on automation completion.
Service levels were fully restored by January 23, 2026 at 08:54, and workflows have been operating in real time since that point.
We had a single instance that had accumulated a very large number of automation workflows configured to trigger on the same event type. Each time an application event occurred, all of these workflows were evaluated simultaneously.
This configuration resulted in tens of thousands of unnecessary database queries per event, which significantly increased system load. As volume grew, the automation system was no longer able to process workflows at the rate they were being generated, causing a backlog and delays for all automation tasks.
In short:
Once the issue was identified, we implemented multiple performance optimizations to reduce unnecessary processing and improve throughput, including:
These changes significantly reduced system load, allowed processing queues to catch up, and restored real‑time workflow execution. Service levels returned to normal by January 23, 2026, and the system has remained stable since.
To prevent similar incidents in the future, we have taken and are continuing the following actions:
These measures are already in place or actively underway and are designed to ensure automation workflows continue to operate reliably as usage grows.
We appreciate your trust and patience, and we’re committed to continuously improving the reliability and performance of the automation experience.