From 076aad83ec7201f9a7a3fae8773b07496765dd19 Mon Sep 17 00:00:00 2001 From: AiAlchemist0 Date: Thu, 27 Aug 2026 23:38:17 -0700 Subject: [PATCH] docs: git branch cron registrations are off by default --- deploy/reference/cron.md | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/deploy/reference/cron.md b/deploy/reference/cron.md index 1ccc1eddb..842661b73 100644 --- a/deploy/reference/cron.md +++ b/deploy/reference/cron.md @@ -1,5 +1,5 @@ --- -last_modified: 2026-03-02 +last_modified: 2026-08-28 title: Cron description: "Scheduling and managing cron jobs in Deno Deploy, including defining cron jobs in code, execution lifecycle, retries, and observability." --- @@ -182,11 +182,20 @@ On the traces page, you can use these cron-related filters: ## Timelines -Cron jobs run on production and git branch +Cron jobs are registered on production and git branch [timelines](/deploy/reference/timelines/). The platform extracts `Deno.cron()` definitions at deployment time and schedules them for execution, so each -timeline runs the set of cron jobs defined in its active revision's code. To -add, remove, or modify cron jobs, update your code and deploy a new revision. +**enabled** timeline runs the set of cron jobs defined in its active revision's +code. + +Production timeline cron registrations are enabled by default. Git branch +timeline cron registrations are disabled by default, so a correctly registered +preview cron can look broken until you turn it on. To enable a branch +registration, open the app's **Cron** tab, select **View Details**, open the +**Enable/Disable** dropdown, and choose `Enable for Git Branch/`. Once +enabled, the job runs against that timeline's active revision. + +To add, remove, or modify cron jobs, update your code and deploy a new revision. Rolling back to a previous deployment re-registers the cron jobs from that deployment. You can see which cron jobs are currently registered in a given timeline from its page in the dashboard.