Deployment troubleshooter

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

Step 1

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

Step 2

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

Step 3

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

Step 4

a. YES – Check status.bitbucket.com.
b. NO – Check deployment log errors in Log Locations: Build and Deploy Logs. Proceed to Step 5.

Step 5

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

Step 6

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

Step 7

a. YES – Login by ssh on 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 process of merging one environment into another, check both environments for running crons. 
b. NO – Proceed to Step 16. 

Step 8

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

Step 9

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

Step 10

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

Step 11 

a. YES – Proceed with Step 12.
b. NO – Proceed with Step 7.

Step 12

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 Magento Cloud 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 a 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 13.

Step 13

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

Step 14

a. YES – Proceed to Step 15. 
b. NO – Proceed to Step 20. 

Step 15

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

Step 16

a. YES – Identify long running processes, kill process, and monitor deployments for reoccurrence.
b. NO – Proceed to Step 17.

Step 17

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

Step 18

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

Step 19

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

Step 20

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