Adobe Commerce deployment troubleshooter

March 7, 2025

Topics:
Build
Deploy
Support

CREATED FOR:

Developer

Stuck deployments and failed deployments on Adobe Commerce can be solved using the Deployment troubleshooter tool. Click on each question to reveal the answer in each step of the troubleshooter.

Step 1 - Verify the service is running

Is Adobe Commerce on cloud infrastructure service up?

Stuck Deployment – Is Adobe Commerce on cloud infrastructure service up? Check Adobe Commerce Cloud.

a. YES – Proceed to Step 2.
b. NO – Maintenance or global outages. Check for estimated duration and updates.

Step 2 - Check deployments in other environments

Are there deployments in other environments that are blocking the deployment in the existing environment?

To get a list of ongoing activities run the following command using magento-cloud CLI (if you have only been added to one cloud project). Note: Check you are on the latest version of magento-cloud CLI. For steps, refer to Update the CLI in the Commerce on Cloud Infrastructure guide.

magento-cloud --state=in_progress

To get a list of ongoing activities run the following command using magento-cloud CLI (if you have been added to multiple projects):

magento-cloud -p <project-id or project-url> --state=in_progress

To find information about an existing deployment activity (refer to Checking deployment log if Cloud UI has “log snipped” error
for details) you can run this command to obtain a running log of that activity:

magento-cloud activity:log <activity-id> [OPTIONAL: <-p project-id or project-url>]

a. YES – Troubleshoot the other environment blocking deployment in the existing environment. Proceed to Step 3.

b. NO – Troubleshoot the current environment. Proceed to Step 3.

Step 3 - Verify SSH on all nodes

SSH successful to all nodes?

a. YES – Proceed to Step 4.
b. NO – Submit a support ticket.

Step 4 - Verify all services running

All services running?

a. YES – Proceed to Step 5.
b. NO – Submit a support ticket.

Step 5 - Verify Bitbucket running

Using Bitbucket?

a. YES – Check status.bitbucket.com.
b. NO – Check deployment log errors in the Build and Deploy logs. Proceed to Step 6.

Step 6 - Check error codes

Error code reported?

a. YES – Proceed to Step 7.
b. NO – Proceed to Step 8.

Step 7 - 403 Forbidden error

403 Forbidden?

a. YES – Proceed to Step 16.
b. NO – Proceed to Step 9.

Step 8 - Verify cron jobs running

Are cron jobs currently running? Log in by ssh on the branch and run ps aufxx |grep cron.

a. YES – Log in by ssh on the affected branch (e.g., primary). Kill and unlock cron jobs. This will kill cron jobs and reset the status. Run php vendor/bin/ece-tools cron:kill and then php vendor/bin/ece-tools cron:unlock. If you were in the process of merging one environment into another, check both environments for running crons.
b. NO – Proceed to Step 17.

Step 9 - Application deployable to remote cluster error

Unable to upload application to the remote cluster error?

a. YES – Proceed to Step 10.
b. NO – Proceed to Step 11.

Step 10 - Check sufficient storage

Available storage okay?

a. YES – Proceed with Step 11.
b. NO – Review Manage disk space.

Step 11 - Verify disk space

file could not be written Warning?

a. YES – Please increase the disk value in .magento.app.yaml and redeploy. If this does not work, submit a support ticket.
b. NO – Proceed with Step 12.

Step 12 - Environment redeployment failed error

Environment redeployment failed error?

a. YES – Proceed with Step 13.
b. NO – Proceed with Step 8.

Step 13 - Check for Elasticsearch upgrade fail

Elasticsearch being upgraded or deployed?

a. YES – Elasticsearch failed upgrade steps. Refer to Elasticsearch software compatibility. If the Elasticsearch upgrade still doesn’t work, submit a support ticket. Note: On Adobe Commerce on cloud infrastructure, please be aware that service upgrades cannot be pushed to the production environment without 48 business hours’ notice to our infrastructure team. This is required as we need to ensure that we have an infrastructure support engineer available to update your configuration within the desired timeframe with minimal downtime to your production environment. So 48 hours prior to when your changes need to be on production, submit a support ticket detailing your required service upgrade and stating the time when you want the upgrade process to start.
b. NO – Proceed to Step 14.

Step 14 - Check space limits

File system out of inodes or space?

a. YES – See Manage disk space.
b. NO – Proceed to Step 15.

Step 15 - Elasticsearch version error

Error about Elasticseach versions?

a. YES – Proceed to Step 16.
b. NO – Proceed to Step 21.

Step 16 - Verify Composer config

Composer config correct?

a. YES – Proceed to Step 10.
b. NO – Review Composer Troubleshooter webpage.

Step 17 - Check for long running processes

Long running processes(es)?

a. YES – Identify long running processes and then kill processes:

Run the following command in the terminal: ps aufx.
Locate the PID of the long-running process.
Terminate the process using kill -9 <PID>.

Monitor deployments for reoccurrence.

b. NO – Proceed to Step 18.

Step 18 - Check for post hook failure

Post hook failure/hang?

a. YES – Database: Free disk space, corruption, incomplete/corrupted tables.
b. NO – Proceed to Step 19.

Step 19 - Check if third-party extensions block deployment

Using third-party extensions?

a. YES – Try Disabling the third-party extensions and running the deployment (to see if they are the cause of the problem), especially if there are extension names in any errors.
b. NO – Proceed to Step 20.

Step 20 - Check for slow queries

Long running queries?

Check slow query log and MySQL show processlist.

a. YES – Kill any long running queries. Review MySQL Kill Syntax.
b. NO – Submit a support ticket.

Step 21 - Downgrade Elasticsearch version

Downgrading Elasticsearch versions?

a. YES – Can’t be done through configuration. Submit a support ticket.
b. NO – Submit a support ticket.

Back to Step 1

recommendation-more-help