Workflow jobs and workers

Workflow screen

From Admin → Workflow, review background operations. Job detail shows type, domain, state, attempts, owner or lease, heartbeat, last error and history according to the release.

Lifecycle

A typical flow is:

queued → claimed → running → completed
                    ↘ retry / failed

A worker claims one job, sends heartbeats and reports the result. The lease mechanism enables recovery if the process stops.

Operator actions

Use Pause, Resume, Retry or Cancel only when supported by the job type. Before retrying, read the last error and correct the cause. For a stale job, verify the systemd service and heartbeat before releasing the lease.

Workers

Mail Flow Worker handles delivery, Workflow Worker executes general tasks, Migration Worker processes imports, and Monitoring/SLA Worker collects state and raises alerts. A stopped worker does not necessarily mean the database is damaged; inspect the specific queue and service logs.