Schedule a Routine
Give an Agent instructions to run once or on a recurring schedule.
A Routine is saved, scheduled work. A Run records an occurrence and its outcome.
Use a Routine for a task whose inputs, permission, and destination are clear. For example: “Each Monday, summarize the release notes and post the summary in our release Space.”
Create a Routine
- Open Team → Routines and choose the create action.
- Write the Instructions, including the input and expected output.
- Set Visible to to Only me or Team. Choose the Agent that will do the work.
- Set the schedule. Check the timezone in the advanced settings for recurring work.
- Choose Send results to. Check the audience of that conversation.
- Choose Create. Review the saved schedule and destination.
Before creating the Routine, make sure the Agent can access its inputs and destination. For a Local Agent, connect its computer and check its working folder. Start with a small task that you can review at the first scheduled time.
Use only destinations you can access. If your editor offers Personal and Team visibility, remember that visibility and output destination are separate: personal instructions can still publish to a shared Space you select.
Make the instructions self-contained
Specify the source, reporting period, output, and permitted actions. For example:
Read the release notes linked below for the previous seven days.
Summarize what changed and link each source.
If nothing shipped, say so. If a source is unavailable, name it.
Do not create issues or change releases.
Sources: [replace with the release-note URLs the Agent can access]Set the weekly schedule and result destination in the form. The text above does not configure those fields.
Scheduled work may run while you are away. A task that needs an interactive sign-in or new approval can fail or need attention.
Check Run history
Open the Routine to review its history. Use View result or the completed result link to open the published answer.
Check failed Runs for the reason. A skipped Run means the occurrence did not execute; it is not a successful result.
For the first Run, check both the history entry and the answer in the destination. Open the linked sources and confirm that the reporting period is correct. A saved Routine is only the schedule; the result is the work you requested.
Use Run status to interpret the history. If no work ran, see Routine skipped. If an answer is missing, see Routine result missing.
Pause, change, or stop
Pause prevents future scheduling. It does not prove that a Run already in progress stopped. Use the running work's controls when a stop is needed.
After editing, check the schedule, timezone, Agent, and destination again. Do not assume an instruction change reruns a completed one-time Routine.
The Agent and visibility scope are fixed after creation. Create a new Routine if either needs to change. Pause the old schedule when you no longer want it to run.
For a Local Agent Routine, its computer must be available when execution is attempted.

