Menu

The migration that kept running after the rollback
📰

The migration that kept running after the rollback

DEV Community: cicd·Kashif Manzer·17 days ago
#24tvKl5c
#devtocicd#devto#dev#migration#database
Reading 0:00
15s threshold

You push a deploy. The dashboard accepts it. Then nothing happens.

No error. No crash. No failed build log to read. Your live service keeps serving traffic happily, as if nothing is wrong. The deploy just sits in the queue, waiting for a worker that never picks it up.

That is what happened at Render on Wednesday, October 14, 2026. Between 12:12 and 15:08 PDT, builds and deploys across all regions failed to start, stalled, or were badly delayed, in two periods of impact totalling about 2 hours and 20 minutes. Live user services were not affected. Only the machinery that starts new work was stuck.

That split is the clue worth sitting with. When the thing that is already running works fine and the thing that starts new work does not, the problem is usually not the whole platform. It is in the path that new work takes, and in whatever that path shares with something else.

What happened, in order

Render runs an internal job scheduler. It coordinates builds, deploys, and other critical platform operations.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.