Skip to content
← Back to release · 2.1.274
Improvements / v2.1.274

[Claude Code on the web] Retry routines before disabling

CHANGELOG · original

[Claude Code on the web] Changed routines to skip a run and retry for up to 72 hours when the owner's GitHub connection is missing, instead of switching the routine off at the first failed check
Open official changelog ↗

Documentation

Documentation excerpt

Repositories and branch permissions

Scheduled tasks need GitHub access to clone repositories. When you create a scheduled task from the CLI with /schedule, Claude checks whether your account has GitHub access for the repository you ran it from. If it doesn't, Claude adds a setup note naming how to grant it.

[!NOTE]

See GitHub authentication options for the two ways to grant access. On Team and Enterprise plans, an Owner of your Claude organization has to turn on each method before you can use it; see Connect GitHub.

If your GitHub connection is missing or expired when a run is due, the scheduled task skips runs until you reconnect, for up to 72 hours. Reconnect GitHub within that window and the task resumes on its own. After 72 hours without a connection, the task turns off, and you turn it back on after reconnecting GitHub.

Each repository you add is cloned on every run. Claude starts from the repository's default branch unless your prompt specifies otherwise. If a GitHub pull request event triggers the run and the pull request's repository is the task's first repository, that repository starts from the pull request's head commit instead.

Claude pushes its work to a branch prefixed with claude/ unless your prompt directs it to push to another branch. To control which branches a run can push to, use branch protection rules or rulesets on GitHub. For runs on Anthropic-managed infrastructure, and for self-hosted runs that push through Anthropic's git proxy, GitHub applies them to the GitHub access you connected, so a rule that access can bypass doesn't block a run's push. A self-hosted run that pushes with the git credentials your deployment provides is checked against those instead. See Configure git.

Documentation snapshot · 2026-11-20

Change details