Background jobs

Lists every scheduled job running inside KPImailer - report schedules and system maintenance alike - with its cron expression, last and next run, and status.

Permissions

Found in Settings → Background jobs, an administrator-only area.

Steps

1. Open Settings → Background jobs. The table lists every job by Name, Schedule (cron expression), Last Run, Next Run, and Status.

   

   Each report’s own schedule appears here too, prefixed report: followed by its ID, plus system maintenance jobs like report-log-retention, audit-event-cleanup, application-log-retention, alerting-event-retention, database-backup, expired-refresh-token-cleanup, and expired-email-token-cleanup.

2. Select a job’s name to open its detail page.

   

3. From the detail page, Trigger Now runs the job immediately, Pause stops it from running on schedule (without deleting it), and Delete Job removes it entirely. The Execution History table below shows past runs.

4. If a job is missing or stuck, use Restore Jobs on the main Background jobs page to re-register the standard system jobs.

Worked example

A report’s schedule looks correct in its editor, but it isn’t firing. An administrator opens Settings → Background jobs, finds the report: entry for that report, and checks its Status and Last Run - if it shows Idle with a sensible Next Run, the schedule is fine and the issue is elsewhere; if it’s missing entirely, Restore Jobs re-registers it.

Caution

Delete Job on a system maintenance job (like database-backup or report-log-retention) stops that maintenance from running until you use Restore Jobs to bring it back - don’t delete system jobs to “clean up” the list.

Tip

Trigger Now is a quick way to test a report’s schedule or force a maintenance job to run immediately, without waiting for its next scheduled time or changing the schedule itself.