From 393bb5065d2ccf2b2ef63a750ebbf6fb459b5d74 Mon Sep 17 00:00:00 2001 From: Viswa Marepalli Date: Thu, 12 Nov 2026 12:29:50 +0000 Subject: [PATCH] docs(agents): clarify schedule first-run timing --- docs/docs/agents/schedules-and-queue.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/docs/agents/schedules-and-queue.md b/docs/docs/agents/schedules-and-queue.md index 522db1d..6caee7c 100644 --- a/docs/docs/agents/schedules-and-queue.md +++ b/docs/docs/agents/schedules-and-queue.md @@ -62,6 +62,9 @@ five years, raises `InvalidCronExpressionError`. await self.schedule_every(timedelta(hours=1), self.sync_feeds) ``` +The first run happens one `interval` after you call `schedule_every`, not +immediately. + If a run is still in progress when the next one is due, the SDK skips the next one. A run counts as hung after `options.hung_schedule_timeout`, 30 seconds by default, and then the schedule runs again.