Worker, provisioning or scheduled task failed

Prerequisites and authority

Start with read-only checks and authorized records. Capture evidence before changes. Stop and escalate when data replacement, financial changes or wider outages are possible.

Worker or provisioning operation failed

Basic

Locate the operation in System Operations. Read status, counts, trigger and error rather than assuming the initiating screen stalled.

Intermediate

Check worker progress and the named dependency. For provisioning, inspect entitlement, router reachability and account/profile state. For imports, inspect row/batch results before resubmitting.

Advanced

Capture bounded worker logs and compare a successful nearby run. Identify lock, retry, schema or configuration failures. Establish whether the job is safe/idempotent to repeat.

Repair the dependency and use the supported manual trigger. Avoid parallel duplicates or a broad Run All without understanding the failure. If the run repeatedly fails, stop and escalate the exception.

Verify its business outcome and the next scheduled run. A completed status with failed targets still needs attention. Retain operation IDs and target-level failures for later code alignment.