Automate work with scheduled tasks changedroutines
Upstream edited this page at 24 Oct 2026 23:14 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 24 Oct 2026 23:37 UTC.
Upstream edited
Recorded here
Lines+24added
Lines−4removed
From line
289
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits42to this page, all time
### "The last run" warnings
The whole hunk
from line 289, old and new numbered
/
from line 289
289289
290290#### Supported events
291291
292GitHub triggers can subscribe to either of the following event categories. Within each category you can pick a specific action, such as `pull_request.opened`, or react to all actions in the category.
292Choose an event from any of the following categories. Within each category you can pick a specific action, such as `pull_request.opened`, or react to all actions in the category.
293293
294294| Event | Triggers when |
295295| :- | :- |
296296| Pull request | A PR is opened, closed, assigned, labeled, synchronized, or otherwise updated |
297297| Release | A release is created, published, edited, or deleted |
298| Issue | An issue is opened, edited, closed, reopened, labeled, assigned, or otherwise updated |
298299
299300#### Filter pull requests
300301
from line 330
329330
330331Click any run to open it as a full session. From there you can see what Claude did, review changes, create a pull request, or continue the conversation. Each run session works like any other session: use the dropdown menu next to the session title to rename, archive, or delete it.
331332
332> [!NOTE]
333>
334> A green status in the run list means the session started and exited without an infrastructure error. It does not mean the work your prompt describes succeeded. Open the run to read the transcript and confirm what Claude actually did. Blocked network requests, missing connector tools, and failures in the work itself all surface there rather than in the status indicator.
333Under **History** on the task's detail page, each finished run's row ends with **Error** if the run failed, **Cancelled** if it was cancelled, and neither word if it succeeded. The **Status** filter names the same three outcomes **Failed**, **Cancelled**, and **Succeeded**. These outcomes say how the session ended, not whether Claude completed the work your prompt describes, so open the run and read its transcript to see what happened.
335334
335* **Succeeded**: the session ended without Claude Code reporting a failure. Blocked network requests, missing connector tools, and work Claude couldn't complete appear in the transcript rather than on the row
336* **Failed**: the session didn't finish normally. For example, it stopped unexpectedly, ended on an error, or was archived before the run started
337* **Cancelled**: the run didn't fail, and its session was archived. If you archive the session of a run that succeeded, the run changes to **Cancelled**. Nothing in the task needs to change
338
339If a warning appears under **History**, see ["The last run" warnings](#the-last-run-didnt-start).
340
336341### Edit and control scheduled tasks
337342
338343From the detail page you can:
from line 499
494499### "Routines are disabled by your organization's policy"
495500
496501An Owner in your Team or Enterprise organization has likely turned off the **Scheduled tasks (Was Routines)** toggle at [**Organization settings > Capabilities > Remote sessions**](https://claude.ai/admin-settings/capabilities). On Claude Code v2.1.227 or later, the same toggle also hides `/schedule` in the CLI. This is a server-side organization setting, so it cannot be overridden from your local configuration. Ask an Owner to turn scheduled tasks back on for your organization.
502
503### "The last run" warnings
504
505When a warning under **History** begins with "The last run", find it in the first column and do what its row says. The warning clears once a later run starts.
506
507| Warning | What to do |
508| :- | :- |
509| "The last run didn't start because your organization had reached its limit on cloud sessions running at once." | The task needs no change. Click **Run now** later, or wait for the next run |
510| "The last run didn't start because its cloud environment couldn't be found or used." | On the task's detail page, open the menu next to its name, select **Edit**, and find the [cloud environment selector](#environments-and-network-access). If it reads **Unavailable environment**, that environment was archived or is no longer available to your account, so choose another one there and save your changes. Otherwise, retry with **Run now** on the detail page, or pick another environment in the selector and save your changes |
511| "The last run was blocked because it couldn't access something it needs, or your organization's policy doesn't allow it." | Check that your [GitHub access](#repositories-and-branch-permissions) covers the task's repositories. If it does, ask an [Owner](https://code.claude.com/docs/en/server-managed-settings.md#access-control) of your Claude organization whether a policy blocks the task |
512| "The last run didn't start because of a problem that's usually temporary." | Click **Run now** to try again, or wait for the next run |
513| "The last run didn't start because its repository or branch wasn't available." | Check on GitHub that each repository in the task has the [branch the run starts from](#repositories-and-branch-permissions). Also check that your [GitHub access](#repositories-and-branch-permissions) covers each repository, and reconnect GitHub if your connection expired |
514| "The last run didn't start because some of its settings weren't accepted." | On the task's detail page, open the menu next to its name and select **Edit**. The dialog doesn't mark which setting wasn't accepted, so check each one there, including the task's name, prompt, model, repositories, environment, connectors, and triggers |
515| "The last run stopped because a usage limit was reached." | For when the task's runs can start again after a usage limit, see [Usage and limits](#usage-and-limits) |
516| "The last run failed." | Click **Run now** to try again, or wait for the next run. The failed run has no session to open |
497517
498518## Related resources
499519
No line in this hunk matches that.