Documentation

Tasks

Use tasks to monitor recurring platform maintenance such as backups, cleanup, agent status checks and mirror sync.
Tasks live under System > Tasks in the admin menu. They are background cron jobs used by DCIM to keep the platform healthy without requiring manual action every day.
Use this page when you need to confirm that scheduled maintenance is running, when a scheduled backup did not happen, when old logs are not being cleaned, or when an agent status looks stale.
Tasks are different from Jobs. Jobs usually represent infrastructure operations requested by a user. Tasks are recurring system maintenance operations.

Scheduled tasks

The top table shows each configured task, its current schedule state, last run, next run, error summary, cron interval and active state.

Status

Status describes the schedule state. RUNNING means the task is enabled and scheduled. DISABLED means it will not run automatically. NEVER_RUN means it is enabled but has no completed run yet. MISSED means the task should have run since the last recorded run.

Last Run and Next Run

Last Run shows when the task last started. Next Run is calculated from the cron interval. If Next Run is Never, the task is disabled or the schedule cannot be calculated.

Error

Error shows the last failed execution summary. Use it as a quick signal, then open the execution history entry for the full result and error payload.

Interval

Interval is the cron expression used by the scheduler. Some tasks also show a human-readable schedule such as Every 5 minutes or Daily at 03:00.

State

State shows whether the task is currently ACTIVE or INACTIVE. Inactive tasks remain configured but do not run automatically.

Default tasks

DCIM installs a default set of tasks. The exact schedule can be changed by settings or future releases, but these are the operational areas they cover.

Delete Expired OTP Codes

Removes expired one-time login or verification codes. This keeps authentication tables clean and reduces stale security data.

GeoIP Database Update

Updates MaxMind GeoLite2 databases when GeoIP is enabled and MaxMind credentials are configured in System settings.

Sync Agent Status

Checks agents and updates their online or offline state. If an agent appears stale, this task is one of the first places to check.

Expire Remote Console Sessions

Cleans up stale remote console sessions and creates cleanup jobs when a running console session has expired.

Create Scheduled Backup

Creates scheduled backups using the current backup target and backup settings. Backup configuration is explained in Backups & restore.

Cleanup tasks

DCIM includes cleanup tasks for old task logs, old dashboard logs and old completed jobs. These keep operational history useful without letting tables grow forever.

Sync Mirrors

Syncs release and profile mirror metadata used by provisioning features.

Enable, disable and reload

Task actions are available only to users with task management permission. If the action buttons are not visible, your account cannot manage tasks.

Change Status

Use the power action to enable or disable a task. Disabling a task stops future automatic runs. It does not delete previous execution history.
Disable tasks only when you understand the effect. For example, disabling agent status sync can make agent status look outdated, and disabling scheduled backup stops automatic backups.

Reload Task

Use reload when you want DCIM to run an enabled task immediately and refresh its data. Reload is disabled for inactive tasks.
After reloading, check the execution history. Some tasks may finish quickly, while others can take longer depending on external services, backup size or the number of records being processed.

Execution history

The lower table shows previous task runs. Use it to confirm whether a task ran, how it finished and what result or error was recorded.

Script and Description

Script identifies the task function. Description explains the execution, such as creating a scheduled backup, synchronising agent status or deleting old logs.

Execution status

PENDING means a task log exists but execution has not started. PROCESSING means the task is running. COMPLETED means the task finished successfully. FAILED means the task recorded an error.

Started At and Completed At

These timestamps show how long the task took and whether it is still running. A processing task normally has a start time without a completed time.

Result and Error

Click a history entry to open the drawer. The drawer shows the structured result and error payload. Use Result to verify what the task changed, and Error to understand why a failed task stopped.

Filters

Filters help you focus on one task or one problem window instead of reading the entire execution history.

Name and Status

Filter by Name when you are investigating one task, such as scheduled backups or agent status sync. Filter by Status when you only want failed or processing executions.

Has Error

Use Yes to show executions with an error payload. Use No when you want successful or clean executions.

Started at and Completed at

Use date ranges when you know approximately when the task should have run, such as after a backup window or after a maintenance period.

Troubleshooting order

If a task is not running, check whether it is active, whether the cron interval is correct and whether the last status is MISSED or FAILED.
If the task failed, open the latest execution entry and read the error payload. Then check the related feature page, such as Backups, Agents, Remote console or System settings.

Tasks video

Temporary video placeholder for tasks
Temporary placeholder. This will be replaced with the real tasks video.