System operations and task controls

Prerequisites and authority

Use an individual staff account with the action permission and required organization module/license. Viewing a menu does not establish permission to mutate records.

Use System Operations

System Operations presents background work independently from the screen that initiated it. Locate the relevant worker/run by type, time, trigger and status. Inspect counts and error details before deciding to rerun it.

1. Confirm whether the operation is waiting, running, completed or failed.
2. Match its target to the affected customer, payment, router or batch.
3. Check processed/succeeded/failed counts as well as the overall status.
4. Inspect the dependency named by the error.
5. Use an authorized manual trigger only when the operation is safe to repeat.
6. Retain the new run identifier and compare outcomes.

A failure count is meaningful even if the run completed. A long-running status may represent a slow job, interruption or stale state; avoid initiating duplicate work blindly.

Manual runs do not replace healthy scheduled execution. After repairing a worker, verify its next scheduled run too. Use Health checks, background services and workers for service health and Background worker and operations reference for the worker inventory.

If an operation repeatedly fails, stop retries and capture the exact error, version, timestamp and affected identifiers. Correct the dependency or code through the later alignment process rather than editing totals to make the operation look successful.

Related guides

Related guides: Staff accounts, roles and permissions, Administrative session and audit investigation, Roles and permission matrix.