Skip to main content
Start with the symptom. Each answer links to the page with the details.

The application is offline

1

Read its state

Call GET /v1/apps/{appId} and look at status, currentResourceMetrics.online, suspension and shutdownNotice.
2

Match what you found

3

Check your plan

When the plan ended, applications and databases are turned off. See plan ended.
4

Read the logs

Follow GET /v1/apps/{appId}/logs and start the application again. The last lines before it stopped usually show the error of your code.

A change did not apply

Most changes made with update only apply on the next start or restart. Check restartRequired in the response: when it is true, call restart. Databases work the same way for the memory.

The request failed

Use the HTTP status, not the message, to decide what to do.
Before starting an application, check currentResourceMetrics.online. Starting one that is already running returns 500.

The application cannot reach a service

If it works for a while and then stops, you may be hitting the limit of requests to the same address. See too many requests. To reach your database, use the host and port in connection, and the password you stored. See databases.

Still stuck

Ask on Discord. Tell us the application name, what you called and the status you got, and never send your API Key or the password of a database.