App Platform Error Code Reference
App Platform is a Platform-as-a-Service (PaaS) offering that allows developers to publish code directly to DigitalOcean servers without worrying about the underlying infrastructure.
During your use of the App Platform, when taking actions that create, update, or redeploy your application or resources, you may encounter one of the following errors. After reviewing the error code below, you can attempt to follow the suggested troubleshooting techniques.
Review some common troubleshooting techniques for App Platform.
Generic Internal Error
Type: InternalError. An internal error occurred. Try reloading or refreshing the page. If you’ve encountered this during a deployment, attempt to manually redeploy your app. Contact support if this persists.
Build Errors
| Error | Type | Reason |
|---|---|---|
| Job Failed | BuildJobFailed |
Your build job failed. See the logs for details. Attempt to correct the problem and redeploy your application. |
| Non-Zero Exit | BuildJobExitNonZero |
Your build job failed because it returned a non-zero exit code. See the logs for details. Attempt to correct the problem and redeploy your application. |
| Timeout | BuildJobTimeout |
Your build job failed because it timed out after 60 minutes. |
| Out of Memory | BuildJobOutOfMemory |
Your build job failed because it was out of memory. |
| Previous Build Reused | PreviousBuildReused |
Your previous build was reused. For efficiency, this is a normal occurrence when nothing significant has changed between two versions of your application. No user action is required, but to view your latest build logs you may need to go back through your Deployment History. |
| Rate Limit Reached | BuildRateLimit |
Your build job is being rate-limited due to concurrent build limits. App Platform will automatically retry your build. If App Platform continues to report this error, wait until your other apps have finished building and try deploying your application again. |
Database Errors
| Error | Type | Reason |
|---|---|---|
| Database Not Available | DatabaseNotAvailable |
Your database is not available. |
| Database Not Found | DatabaseNotFound |
Your database was not found. |
| Database Limit Exceeded | DatabaseLimitExceeded |
Your database limit was exceeded. |
Deploy Errors
| Error | Type | Reason |
|---|---|---|
| Run Command Not Executable | ContainerCommandNotExecutable |
Your deploy failed because your container run command either didn’t exist or was not executable. You can try clearing any custom run commands from your application resources’ configurations. Then, after a successful deployment, use the Console functionality in App Platform to test out variations of your run command interactively. |
| Non-Zero Exit Code | ContainerExitNonZero |
Your deploy failed because your container exited with a non-zero exit code. See the logs for details. Attempt to correct the problem and redeploy your application. |
| Health Checks | ContainerHealthChecksFailed |
Your deploy failed because your container did not respond to health checks. If a health check is failing, that means that external traffic is not reaching your service at the expected HTTP route. |
| Out of Memory | ContainerOutOfMemory |
Your deploy failed because your container was out of memory. |
| Resource Exhausted | ResourceExhausted |
By default, your overall App Platform resource usage is limited per account or team. There are limits on the total number of apps, total memory usage across apps, total CPU count across apps, total number of static sites, total number of domains, and total active build count. If you need any of these limits increased, contact support. |