Skip to content

docs: git branch cron registrations are off by default #3464

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AiAlchemist0 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: git branch cron registrations are off by default #3464

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 13 additions & 4 deletions deploy/reference/cron.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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."
---
Expand Down Expand Up @@ -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/<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.
Loading