Retool: Workflows Stuck in Pending State

Impact: majorStatus: resolvedStarted 2026-07-30 20:22 UTCResolved 2026-07-31 05:52 UTC (9.5 h)5 updatesSource: stspg.io

Summary

Retool Workflows experienced a major degradation: workflows were stuck pending, with increased 429 rate limit responses for start triggers. The incident began at 2026-07-30 20:22 UTC and was resolved at 2026-07-31 05:52 UTC, lasting 9 h 29 min. A fix was deployed at 07-30 21:20 UTC, with workflows still degraded but recovering.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Retool-managed Temporal (via Temporal.io)Workflows

Timeline of updates

investigating2026-07-30 20:22 UTC
We are investigating an issue with Retool Workflows being stuck in a pending state. There is also an uptick in 429 rate limit responses for start triggers
identified2026-07-30 20:45 UTC
We've identified the issue and are working on a fix.
monitoring2026-07-30 21:20 UTC
The fix has been deployed, and we're monitoring the results. Workflows are still degraded but recovering.
monitoring2026-07-30 23:08 UTC
We are continuing to monitor for any further issues.
resolved2026-07-31 05:52 UTC
This incident has been resolved.

Rewindex changes for this incident

Major incident: Workflows Stuck in Pending State 2026-07-30 20:22 UTC

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Retool profile · Recent Retool incidents · Markdown · JSON