My run is stuck, paused or failed

What to do when a studs.gg run seems stuck, is paused or fails: when to stop and retry, how to resume, and what each failure message means.

It seems stuck

Runs can be quiet for a while during long steps, and a run is only stopped automatically after 150 minutes. If nothing has changed for a long time and you would rather start over, press Stop, then retry. Stopping is charged for the work done so far.

It is paused

A run is paused, with its progress saved, when it runs out of credits or hits a problem on our side that is likely to clear. The message on the run says which. Claim your daily credits or upgrade if credits were the reason, then click Resume. A run can be resumed up to three times. Sending a new message in the project discards the paused run.

It failed

Read the message on the run, it says what to do:

  • "This usually self-recovers. Please try again." A problem on our side. Click retry to run the same idea again without retyping.

  • "Please reword your prompt and try again." The plan or scripts for this idea did not come together. Make the idea smaller or more specific and try again.

  • "Some areas of your game couldn't be built" Most of the game shipped. See Parts of my game are missing.

  • "Your new prompt is too different from this project's existing design." Start a new project for the new idea.

  • "You don't have enough credits to start a new run." Claim your daily credits, or upgrade to Pro. See How credits work.

  • "Please sign in with Roblox again." Your Roblox session expired. Sign in again and start a new run.

Only failed or stopped runs can be retried, and a retry is a new run with its own cost.

Still stuck

Click your avatar and choose Help & Support. It shows the details we need, including your Run ID. Email those to support@studs.gg along with the exact message you saw, or use /support in our Discord. If it failed because of something on our side, tell us and we will make it right.

Updated 14 October 2026

More help

MarkdownRSS feed