outages.live
Live
RetoolIncident ·

Source Control Deployments Stalled

ResolvedOfficial update

This incident has been resolved.

The latest update from Retool.

State

Resolved

Started

Lasted

1 h 33 min

Worst impact

Degraded

Timeline

5 updates
22:4423:0723:3023:5300:16
DegradedUpdate postedTimes in UTC

Investigating

12 min 12%

Identified

30 min 32%

Monitoring

51 min 55%

Updates

Times in UTC

As posted by Retool

Resolved

This incident has been resolved.

Monitoring

The fix has been deployed and source control deployments should be working as expected -- we are monitoring.

Monitoring

A fix is being deployed and we are monitoring.

Identified

We've identified the issue and are working on remediation.

Investigating

We are investigating an issue with Source Control deployments being stalled in a "queued" state on Retool Cloud version 4.74.0

Affected components

1
Source Control

Retool in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

17

Median duration

3 h 26 min

This incident

55% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 days
median 3 h 26 min
90 days agoToday

Other Retool incidents

All incidents

Retool·Elevated Latency on Query Execution (Retool Cloud)

Query performance is back to normal and the incident is resolved.

Resolved

Retool·Elevated Latency on Query Execution (Retool Cloud)

This incident has been resolved.

Resolved

Retool·Retool MCP connection errors

This incident has been resolved.

Resolved

Retool·Retool MCP connection failures

This incident has been resolved.

Resolved

Retool·Errors running generic JDBC resource type queries

This incident has been resolved.

Resolved

Follow Retool

Your coding agent knows when Retool is down, and tells you when a failure is theirs, not yours. You can also get Retool incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "retool" and tell me if Retool has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=retool
Slack
/feed subscribe https://outages.live/feed.xml?providers=retool

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane