After July 2021, the 2.3.x release line no longer received quality updates or user guide updates. PHP 7.3 reached end of support in December 2021, and Adobe Commerce 2.3.x reached end of support in September 2022. We strongly recommend upgrading to Adobe Commerce 2.4.x to help maintain PCI compliance.

Cron (Scheduled Tasks)

This site contains archived merchant documentation for a version of Adobe Commerce and Magento Open Source that has reached end-of-support. The documentation available here is intended for historical reference only and is not maintained. The Adobe Commerce Merchant Documentation for current releases is published on the Adobe Experience League.

Magento performs some operations on schedule by periodically running a script. You can control the execution and scheduling of Magento cron jobs from the Admin. Store operations that run according to a cron schedule include:

In addition, you can configure the following to run according to a cron schedule:

  • Order System Grid Updates and Reindexing
  • Pending Payment Lifetime

Make sure that the base URLs for the store are set correctly, so the URLs that are generated during cron operations are correct. See Set up cron jobs in the developer documentation.

Configure Cron

  1. On the Admin sidebar, go to Stores > Settings > Configuration.

  2. In the left panel, expand Advanced and choose System.

  3. Expand Expansion selector the Cron section.

    Advanced configuration - cron tasks Cron (Scheduled Tasks)

  4. Complete the following settings for the Index and Default groups.

    The settings are the same in each section.

    Generate Schedules Every Defines how often the schedule is generated (in minutes). Schedules are stored in the database.
    Schedule Ahead for Defines how far in advance cron jobs will be scheduled (in minutes). For example, if this setting is set to 10and the cron runs, cron jobs will be scheduled for the next 10 minutes.
    Missed if not Run Within Defines the time (in minutes) that, if the cron job is not run after its scheduled time, it cannot be run, and its status is set to Missed.
    History Cleanup Every Defines the time (in minutes) that the history of ended tasks is cleared from the database.
    Success History Lifetime Defines the time (in minutes) for which the history of cron jobs with a Successful status remain in the database.
    Failure History Lifetime Defines the time (in minutes) for which the history of cron jobs with an Error status remain in the database.
    Use Separate Process Defines whether all cron jobs from the group are run in a separate system process. Options: Yes / No

    Advanced configuration - cron group index Cron Group Index

  5. When complete, click Save Config.

© 2024 Adobe. All rights reserved.