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.
a. YES – Proceed to Step 2.
b. NO – Maintenance or global outages. Check for estimated duration and updates.
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 16.
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 13.
a. YES – Identify long running processes, kill process, and monitor deployments for reoccurrence.
b. NO – Proceed to Step 17.
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.