Troubleshooting

When a deploy fails, GetFlowing tells you why in plain English. A build that fails changes nothing, and a new version that never passes its health check never takes traffic, so the version that was running keeps running. These pages list the messages you are most likely to see, what each one means, and what to do. They are also listed together in Failure messages.

Find out whyCopy Anchor Link

• The app's Overview shows where the last deploy stopped, what to change, the file and line where GetFlowing can tell, and the last lines of the error.
• Copy for your assistant copies that whole report, ready to paste into Claude, ChatGPT, Cursor or Codex.
• The app's History tab says the same, and so does its chat on plans with the agent.
• A connected assistant can read it too, with explain_deploy_failure and get_recent_logs. See AI assistants.

What the message saysCopy Anchor Link

• The build failed: the image could not be built, or a download was refused.
• The app does not run: it built, but it crashed or failed its health check.
• The deploy was refused: a plan limit, an unpaid plan, the free app's limits, or security findings.

It is on our sideCopy Anchor Link

We couldn't build your app, and it's a problem on our side rather than in your code. Our team has been notified, so please try again shortly.

We hit a permissions problem while setting up your app. Our team has been notified.

Something went wrong setting up your app's cloud resources. We stopped safely and our team has been notified.

Your cloud build capacity is still being set up. On a new account this can take up to a day, so please try deploying again later.

Something went wrong while deploying your app, and we stopped safely so nothing was left half-built. Please try again shortly. If it keeps happening, our team will look into it.

Usually you do not need to change your app. A request is normally raised for GetFlowing's team, and you can follow it on the Help page. Try again a little later.

Still stuckCopy Anchor Link

Ask the GetFlowing team. See Get help.