Skip to main content
For the complete documentation index for agents and LLMs, see llms.txt.

Run Scheduled Calls as Durable RunsBeta

Beta
This is coming — this page describes a feature that's still being rolled out and may not be available to you yet.

Submit each scheduled call of a service as a durable run, so a long scheduled job isn't cut off or lost.


Prerequisites​

Turn On Durable Runs for a Schedule​

A scheduled call on a service is a plain chat request by default. It's cut off at the request time limit, it isn't retried, and it can't resume. For a long scheduled job, such as a nightly or weekly flow, submit each scheduled call as a durable run instead.

  1. Open the service, click Settings, and go to the Scheduled Calls section.
  2. Turn on Run as a durable execution.
  3. Click Save. At the next scheduled time, the run appears in the Active list on the Runs tab.

The switch is off by default. You can also set durable to true in the request body of the schedule's PUT call to the service's cron endpoint.

Each scheduled call is then submitted the same way as a run you start from Connect. It uses the schedule's query and parameters, and it runs as the user who saved the schedule.

  • One run per scheduled time: Each scheduled time gets its own fixed idempotency key, built from the schedule and the scheduled time. If a submission fails after the service accepted the run, the next attempt uses the same key and replays that run instead of starting a second one. External side effects of a run, such as posting a comment, can still happen twice.
  • Deadline for each run: A run must be accepted before the next scheduled time or before the schedule's active window closes, whichever comes first. The deadline is never longer than the service's normal admission window, so for long intervals it can fall before the next scheduled time. The service refuses a run after its deadline, so a scheduled time that the scheduler has moved on from never starts late.
  • Refused submissions: If the service refuses a submission, for example because it has reached its maximum number of unfinished runs, the schedule isn't marked as called. The scheduler retries the same scheduled time until its deadline passes. To free capacity, wait for runs to finish or cancel some. For the limits, see Pausing Durable Runs and Limits.
  • Skipped scheduled times: If the next scheduled time arrives while an earlier one still isn't submitted, the scheduler gives up on the earlier one, logs it as skipped once, and submits the latest due time. If times are skipped often, free capacity as described in the previous item. A scheduled time that falls outside the schedule's active window was never due, so it doesn't count as skipped.
  • Last call time: The Last call value for a durable schedule is the scheduled time that was last handled, not the moment the submission succeeded.
  • Search history: A scheduled durable run doesn't use a search session. It writes its own search history entry, like any other durable run.

To follow a scheduled run, open it on the Runs tab as described in View Durable Runs.