# Show support both the intended local time and the execution instant

A bare timestamp is difficult to explain during a scheduling incident. Keep the rule, zone, version and outcome together in the operational view.

By Cobnex editorial. Published 2026-09-10. Updated 2026-09-11.

## Provide the schedule's meaning

Display the local recurrence and named business zone, with the relevant gap, overlap and missed-work policy. Include the current owner and enabled state.

Keep individual occurrence records linked to the schedule version that created them. A later edit should not rewrite the explanation of a past run.

Use clear timezone labels in support communication rather than assuming every participant reads time in the same location.

## Explain the occurrence lifecycle

Show due, queued, running, completed, missed and superseded states as used by the implementation. Keep worker attempts separate from the occurrence identity.

Record the resolved instant and actual start or completion times so support can distinguish calculation error from processing delay.

Include the safe action for each state. A missed report and an already completed notification should not share an unrestricted rerun button.

## Assign policy decisions

Name the business owner who can decide whether old work should catch up or be skipped. Technical staff should not infer that an expired action remains useful.

Document who can change a schedule's zone or recipient and how queued work is affected. Preserve normal access checks during recovery.

Keep the time-zone data and scheduler maintenance responsibilities with a named engineering owner.

## Rehearse a boundary case

Have the receiving team investigate a synthetic daylight-saving occurrence and a schedule edited after queueing. Ask them to explain the intended and actual times and choose the correct next action.

Resolve gaps in the view or runbook before relying on it during a live incident.

The handover is complete when support can explain why a job ran, did not run or ran late without changing clocks or retrying blindly. That clarity depends on preserving business intent alongside technical timestamps.

## Sources

- [IANA: time-zone database](https://www.iana.org/time-zones)