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 Routines. In the current app this is available from Center Agent; newer workspace navigation places it under Team.
- Choose the create action.
- Write the instructions and expected output.
- Choose the Agent if the editor offers an executor selector.
- Set the schedule and check the timezone.
- Choose where the result should appear.
- Review and save.
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:
Every Monday, read the release notes from the previous seven days. Post a short summary in Release Planning. Link each source. If nothing shipped, say so. Do not create issues or change releases.
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.
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.
For a Local Agent Routine, its computer must be available when execution is attempted.