Adobe Commerce deployment troubleshooter

Stuck Deployment – Is Adobe Commerce on cloud infrastructure service up? Check Adobe Commerce Cloud (under Experience Cloud on the Adobe Status page).

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

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 guide.

magento-cloud --state=in_progress

To get a list of ongoing activities run the following command using magento-cloud (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 shipped” 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>]

• YES – Troubleshoot the other environment blocking deployment. Proceed to Step 3.
• NO – Troubleshoot the current environment. Proceed to Step 3.

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

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

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

• YES – Proceed to Step 7.
• NO – Proceed to Step 8.

• YES – Proceed to Step 16.
• NO – Proceed to Step 9.

ps aufxx | grep cron

• YES – Kill and unlock cron jobs:

  code language-none
  php vendor/bin/ece-tools cron:kill

  php vendor/bin/ece-tools cron:unlock

• NO – Proceed to Step 17.

• YES – Proceed to Step 10.
• NO – Proceed to Step 11.

• Check for Integration/Starter environment

• Check for Pro Staging/Production environment

• YES – Proceed with Step 11.

• NO – Review Manage disk space.

• YES –

  • For Integration/Starter environments: Increase disk value in .magento.app.yaml and redeploy. If this does not work, submit a support ticket. Alternatively, delete large log files:

  code language-none
  ls -la var/log

  • For Pro Staging/Production environments: Submit a support ticket to add storage.

• NO – Proceed with Step 12.

• YES – Proceed with Step 13.
• NO – Proceed with Step 8.

• 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.
• NO – Proceed to Step 14.

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

• YES – Proceed to Step 16.
• NO – Proceed to Step 21.

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

• YES – Kill processes:

  1. Run: ps aufx
  2. Locate PID
  3. Terminate: kill -9 <PID>

• NO – Proceed to Step 18.

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

• YES – Try Disabling the third-party extensions and redeploy, especially if there are extension names in any errors.
• NO – Proceed to Step 20.

Check slow query log and MySQL show processlist.

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

• YES – Can’t be done via configuration. Submit a support ticket.
• NO – Submit a support ticket.