Troubleshooting
What each unavailable or error state means and what to do.
A page is taking too long
The free backend sleeps after 15 minutes without traffic. It can take about a minute to wake, which is longer than a page request waits. Wait about a minute, then retry. Your saved work stays in the database.
If you just submitted something, use the same-request retry or check whether it was saved before starting it again. A timeout does not tell you whether a save reached the server.
“TasteCase isn’t connected to its service yet”
This means the website has no configured API connection. It is different from a sleeping service: the deployment owner needs to fix its settings. TasteCase shows an error rather than made-up data.
Other states
| You see | What it means | What to do |
|---|---|---|
| Couldn’t reach TasteCase | The request may not have arrived, or the answer was lost. | Check your connection. Reload before resending anything you just submitted. |
| Your session has ended | You need to sign in again. | Sign in; you’ll return to the same page. Review drafts are kept in that tab. |
| We couldn’t find … | It doesn’t exist, or it belongs to another account. | Check the link, or go back to your projects. |
| This changed since you loaded it | Someone saved a newer revision. | Load the latest revision; your draft is kept. |
| TasteCase is busy | The service is temporarily unable to answer. | Use the retry button. An unchanged save uses its original request ID. |
| We couldn’t confirm … | The outcome of a save is unknown. | Use “Retry the same …”, or check the latest state first. |
Runner problems
| Symptom | Likely cause |
|---|---|
| Exit code 3 | The token is wrong or was revoked. Issue a new credential. |
| Exit code 4 | The API or your provider is unavailable. Nothing was concluded from the gap. |
| Exit code 5 | The lease expired; the work can be claimed again. |
| “No work” | Nothing is queued for this project, or for the release label you bound. |
See Error codes for the full list.