Cron Manager

VIDEO WALKTHROUGH

Cron Manager: setup guide

2:38

Recorded on version 1.0.9 · Narrated walkthrough · English captions

Jump to a chapter 8 chapters

1. 0:00Set up Cron Manager
2. 0:12Open settings and choose scope
3. 0:32Find configured cron jobs
4. 0:53Review execution history
5. 1:13Configure failure notifications
6. 1:33Use manual execution carefully
7. 1:56Save and verify your setup
8. 2:17Your setup checklist

Read the full video transcript

Cron Manager 1.0.9 — Magento Admin setup

00:00:00 — Set up Cron Manager
Welcome to the Agentic Ecom Cron Manager Admin guide. We'll walk through the main setup screens and the checks to make before using the module. This guide assumes the extension is already installed.

00:00:12 — Open settings and choose scope
Start in Magento Admin and open Stores, Configuration. Choose Cron Manager. Check the Scope selector before editing. Use the appropriate website or store view where the setting supports it. The screen values here are a demonstration; enter the settings and service details that belong to your own store.

00:00:32 — Find configured cron jobs
Open Cron Manager's Jobs screen to inspect the registered cron jobs. Review the job code, group and schedule before taking action. This screen helps you find a particular Magento task; it does not replace the server's cron installation or prove that the operating system is invoking Magento correctly.

00:00:53 — Review execution history
Open the run history and use the available filters to find recent results for the job you are investigating. Compare statuses, timestamps and any saved error information. A missing or failed run needs investigation in the relevant module and server logs before you decide to run a job manually.

00:01:13 — Configure failure notifications
In Error Alerts, choose whether to enable Admin Global Notifications and Email Alerts. Enter the intended alert email address and set a sensible alert interval in minutes. Confirm that Magento can deliver email before relying on notifications, and give the relevant staff permission to review failures.

00:01:33 — Use manual execution carefully
An authorised administrator can run one registered job manually. Check what that job does first: it may send messages, update data or call another service. After a deliberate test, inspect its saved result and history. Deleting historical schedule rows is housekeeping; it does not repair the underlying cause of a failed job.

00:01:56 — Save and verify your setup
When your required settings are complete, use the screen's Save control and wait for Magento's confirmation. Then reopen the record or configuration and check the saved values at the intended scope. If the storefront still shows earlier settings, refresh the relevant caches. Test your own configuration before using it with customers.

00:02:17 — Your setup checklist
That's the Admin setup walkthrough for Cron Manager. Check permissions and scope, review the module-specific settings, then save and verify a small staging example. Use the written guide at user guides dot Agentic Ecom dot net for installation details, complete field references and any separate storefront integration steps.

Download videoEnglish captionsDownload transcript

Cron Manager shows configured Magento cron jobs and their run history in Admin. An authorised administrator can run one registered job manually, review its saved result, delete selected historical schedule rows and configure alerts for failures.

Current AgenticEcom direct-store release: 1.0.9. Adobe Marketplace purchasers should use the version available in their Adobe Composer entitlement; its update is subject to Adobe review. Version 1.0.9 removes a schedule-page layout reference to a block and template that were absent from the package. The schedule grid now renders without that Magento error. The existing job, timeline and alert features remain available.

Where to find it

AgenticEcom → Cron Manager in the Admin sidebar has Cron Jobs Config, Tasks Timeline and Cron Tasks List screens. Settings are at Stores → Configuration → AgenticEcom → Cron Manager and apply at the default scope.

Install

The Composer commands below are for a direct AgenticEcom purchase. If you bought this extension through Adobe Commerce Marketplace, install the purchased package from repo.magento.com with Adobe Marketplace access keys; see Getting Started. A Marketplace purchase does not require a second direct-store licence.

For a direct purchase, find your key on My Licences:

composer config repositories.agenticecom composer https://repo.agenticecom.net
composer config --global --auth http-basic.repo.agenticecom.net <YOUR-LICENCE-KEY> x
composer require agenticecom/module-cron-manager
php bin/magento module:enable AgenticEcom_CronManager
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento cache:flush

Compatibility

Magento

Verified on Magento Open Source 2.4.9. Check release notes for other versions.

PHP

Verified on 8.5.10. Check release notes for other PHP versions.

Manual run

Start one configured job from Admin and save a new history row.

Alerts

Optional Admin and email notifications when a schedule fails.

What you get

Jobs

Configured cron jobs with code, group, handler class and method, schedule expression and a Run Job action.

Recent activity

A table of the latest 100 non-pending schedules, newest first, with status, UTC timestamps and messages. Magento’s schedule grid gives access to older rows and filters.

Schedules

Magento’s cron_schedule table as a filterable grid. You can mass-delete selected historical entries; running rows are skipped.

Run one job manually

1. Open Cron Jobs Config and find the configured job you want to run.

2. Use its Run Job action. Magento’s Admin form key and Cron Manager permission protect the POST action.

3. Review the newly saved schedule row for success or an error message.

Manual runs can repeat business effects

The action only executes jobs registered in Magento’s cron configuration. A manual run can still send emails, change data or repeat another business effect. Select a job whose effect you understand and grant the Cron Manager Admin permission only to appropriate staff.

Failure alerts

At the default Cron Manager configuration scope, enable Admin bell notifications and optionally email alerts. Set a valid recipient for email. Email uses Magento’s configured mail transport and General Contact sender, so the store must be able to send mail. Both alert types are rate-limited per job code by the configured interval (default 60 minutes, allowed range 1–10080 minutes).

FAQ

How do I know if cron is actually running?

The recent-activity table and schedule grid show saved runs and their outcomes. If no new rows appear, check the server’s system cron and Magento’s own logs.

Can I re-run a job that failed without waiting for its schedule?

Yes. Use Run Job in the Jobs grid. Cron Manager creates a new schedule-history row and records success or the error message. Consider whether repeating the job is safe first.

Will the schedule table grow forever?

You can mass-delete selected old cron_schedule rows from the Schedules grid. Running rows are skipped. Filter by status and date first, and use Magento’s standard retention settings for routine cleanup.

Is running jobs from the Admin safe?

Cron Manager only looks up registered jobs by code. Admin actions use POST and a dedicated permission. A job may still have effects such as sending emails or changing data. Check the release notes for tested Magento and PHP versions.