A scheduled run did not happen

An occurrence you expected is not there

A schedule should have produced a run and did not, or it produced one at an hour you did not expect.

Before you submit anything by hand, find out which of those two happened. They have different fixes.

Check the time zone and the intended occurrence

Schedules are evaluated against a configured time zone, not against your local clock. A daylight-saving change moves a wall-clock time without anyone editing the schedule.

Each occurrence carries an identity built from the schedule, its version and the intended occurrence time. Open the schedule events and look for that occurrence. Three answers are possible.

• It exists and produced a run. You are reading the wrong time zone, and the work is done.
• It exists and was skipped. A configured misfire or replay policy decided that.
• It does not exist at all. The schedule was paused, revoked, or its version changed.

Then do this

• Skipped by policy. Read the misfire policy you configured. If the missed occurrence still matters, replay it. Replay reuses the same occurrence identity, so it cannot silently double-run.
• Paused or revoked. Resume the schedule first. Then decide separately whether the missed occurrences should be replayed.
• Version changed. A new schedule version starts a new occurrence series. Confirm which version you expect to fire before you judge it broken.

Check your current spend budget and approval state before creating any run by hand. A schedule that stopped firing because a budget was exhausted will refuse a manual submission for the same reason.

What not to repeat

Never submit a manual run that duplicates an occurrence that already fired. The schedule and your manual submission use different idempotency scopes, so nothing will stop you.

Never fix a time-zone surprise by shifting the scheduled hour. Set the time zone. Shifting the hour looks correct until the clocks change again.

Get help safely

Send the schedule identifier and version, and the intended occurrence time with its time zone. Add the request ID, the operation name, your client version, the contract release, and what you observed instead.

Leave out payloads, key values, signed URLs, and banking information.

Read more about occurrences and replay and pausing, revoking and recovering a schedule.