Manage DirectAdmin Cron Jobs with Safe Scheduling and Verification

DirectAdmin’s user-level Cron Jobs interface can create, edit and remove account schedules. Confirm the correct user, approved application command and timezone before changing recurring work.

Create a user task

1. Sign in to the trusted DirectAdmin panel and open User Level > Advanced Features > Cron Jobs. Theme labels can differ.
2. Select Create Cron Job and review the schedule fields. A star means every permitted value; comma lists, ranges and supported steps express different schedules.
3. Enter the intended command with verified paths and interpreter. Do not assume a command copied from another account has the right home directory or PHP version.
4. Read the installed interface’s schedule hint, save and inspect the resulting entry.

A step such as */2 in the minute field selects alternating minute values within each hour; it is not a promise of a fixed delay measured from the previous task’s completion. When both day-of-month and weekday are restricted, check the actual cron implementation’s matching behavior rather than assuming both must match. Confirm timezone and daylight-saving implications for time-sensitive work.

Output, environment and overlap

Use the Send all Cron output to E-mail setting if available and monitor its delivery. Cron mail generally carries command output; silent success is not necessarily emailed, and mail delivery is not guaranteed monitoring. Keep logs protected and bounded instead of hiding all errors during setup.

Test the application in its intended account context, then verify an actual scheduled result. Cron’s environment differs from an interactive terminal. Consider concurrent runs and use application-supported locking where necessary; creating a schedule does not ensure the last run finishes before the next starts.

Edit or delete with a fresh list

Reload the Cron Jobs page before editing or deleting an entry, especially if another administrator or shell session changed the schedule. Record the original and confirm the exact command, not just its row position. DirectAdmin documents stale-list identifier risks for some configurations. Deleting an entry stops future scheduling, not an already running process or its side effects.

References: current Evolution schedule hints; live listing and stale-entry caution; cron field semantics.

Reviewed October 15, 2026. Documentation review; no DirectAdmin task, application or output email was executed or changed.