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.

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):

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.

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

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

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

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

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

a. YES – Log in by ssh on the integration 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.

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

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

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.

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

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.

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

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

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

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

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

Monitor deployments for reoccurrence.

b. NO – Proceed to Step 18.

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

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.

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.

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