Review automatic draft history and missed cycles
Inspect automatic payroll attempts, open created drafts, skip a cycle, and retry eligible failures.
Steps3 sections
Run history records automatic draft attempts for one schedule. Use it to distinguish a scheduled cycle, a created or existing draft, a skipped attempt, and an attempt needing attention. A saved enabled policy alone is not evidence that a draft was created.
Steps
- Open the schedule's run history
Open Automatic draft settings for the schedule and its Run history. Confirm the organisation and schedule. A draft or notification may also link to its exact execution record.
- Inspect upcoming cycles
Review the period, close-by date, draft time, and schedule timezone. Read any unconfirmed-calendar warning. Use Skip cycle only when offered and when you intend to omit that automatic attempt; this does not retire the schedule or finalise payroll.
- Read the recorded outcome
In Run history, check the status, completed or started time, attempt count, and reason. Use Open draft to inspect a created or already-existing preparation draft. View-only users may see View run instead.
- Resolve the cause before retrying
Follow the recorded reason to repair calendar authority, organisation setup, access, or other named requirements. Select Retry only when the execution is eligible and the action is offered. Then inspect its latest outcome and open the draft if one is available.
Missed cycles and existing drafts
When several cycles became due while execution was unavailable, only the newest canonical due occurrence is eligible for automatic creation. Older unprocessed occurrences remain gaps for manual review; the runner does not keep walking backwards and creating historical drafts on later checks. Review those periods and their payroll coverage before preparing any missing run manually.
An existing draft can be reported as the cycle outcome rather than creating another draft. Open it and check that its captured inputs are current. A skipped or failed attempt does not mean that payroll for the period is complete.
When an attempt needs attention
Check the employee and schedule setup, confirmed business calendar, retirement boundary, and execution availability. For background execution issues, inspect workspace execution settings. Reading or acknowledging a notification does not resolve the recorded cause. Users with payroll automation access can perform the permitted cycle actions; other users may have view-only access.