Solution for deployment failed

Check the deployment logs:

  1. If the deployment had failed during the setup:upgrade step, the cron won’t have been re-enabled.
    For example: you see this line in the deployment log:

    The command "/bin/bash -c "set -o pipefail; php ./bin/magento setup:upgrade --keep-generated --ansi --no-interaction | tee -a /app/$<project_id>/var/log/install_upgrade.log"" failed. Cache types config flushed successfully

  2. Otherwise, the deployment might have failed during some other stage. Check the deployment log and ensure that both lines appear (example below). If you don’t see both lines similar to this in the log, it means that the cron was not re-enabled:

    [2024-03-06T10:55:39.345564+00:00] INFO: Disable cron



    [2024-02-07T10:50:09.579005+00:00] INFO: Enable cron

Submit a Support request if you need further assistance.

Previous pageFix data not updated in Commerce Data Exporter feeds and cron logs errors with changelog table don't exist
Next pageError opensearch search engine doesn't exist. Falling back to livesearch.

Commerce


Put the Customer at the Center and Build Relationships That Last a Lifetime

Online | Strategy Keynote | General Audience

First impressions last a lifetime. Great first impressions feel personal, connected, and relevant right from the start. From the first...

Wed, Mar 19, 2:30 PM PDT (9:30 PM UTC)

Register

Elevate and Empower Teams with Agentic AI for Exceptional Experiences

Online | Strategy Keynote | General Audience

Elevate and empower your CX teams with AI that transforms creativity, personalization, and productivity. Discover how Adobe is...

Tue, Mar 18, 1:00 PM PDT (8:00 PM UTC)

Register

Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more