By eXp
Deployment was triggered by a commit in the connected repo. Build process started, however, after 1 hour, it still shows as pending. Tried to cancel several times, it has no effect.
It happened now on 2 instances at the same time, which are connected to the same repo/branch.
Build logs were empty at the beginning, after ~30minutes of hanging the logs are now showing that build was successful, however the whole process is still stuck at BUILD phase.
Commit was a regular commit, nothing special was changed that I could even imagine causing this. Anyone had similar issue?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi there,
If it’s happening to two apps at the same time on the same repo/branch, that usually could be an App Platform-side hiccup rather than your commit. First thing I’d check is the DO status page and incident history to see if there’s anything ongoing with App Platform deploys in your region: https://status.digitalocean.com
If the build logs say “successful” but the deployment never moves past BUILD and cancel doesn’t do anything, I’d try a rollback to the last good deploy (if available) or trigger a fresh deploy.
If it’s still stuck, I’d open a support ticket with the app ID, region, deployment time, and ideally the deployment ID so they can unstick it on their side: https://do.co/support. For reference, DO also has a general App Platform troubleshooting doc you can follow, but in this case support is usually the fastest path:
https://docs.digitalocean.com/support/how-to-troubleshoot-apps-in-app-platform/
Hi there,
A couple of things you can do that sometimes shakes it loose without changing code. In the App Platform UI, trigger a redeploy using “Force Rebuild and Deploy” and select the option to clear the build cache. That forces a fresh build image and avoids reusing any stale cached layer that might be wedged.
If cancel isn’t working, it’s usually because the deployment job is stuck in the backend queue/worker and the control panel can’t interrupt it. In that case, the most actionable step is opening a support ticket and include the app name, deployment ID, and the timestamp when it started hanging, plus mention that cancellation has no effect and that it happened across multiple apps simultaneously. DigitalOcean’s own troubleshooting flow basically boils down to “check logs, then contact support if it’s an internal/platform issue.”
It’s also worth a quick look at the DigitalOcean status page/history to see if there’s a platform incident around the time you tried deploying. Even if it shows “Operational”, support can still confirm if there was a partial outage or a stuck build queue in a specific region.
Hope that this helps!
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.