A scheduled automation runs a prompt every hour, every weekday morning, or once a week. Each run starts an agent on the repository you pick. The agent opens a pull request when the work needs one.
Use a scheduled automation for routine work, such as updating dependencies or writing a weekly summary.
Create a scheduled automation
- Select Integrations in the sidebar.
- Open Schedule > Automations.
- Select New automation.
- Give it a name.
- Write the Prompt. This is the whole instruction the agent gets. It has the repository checked out and can open a pull request.
- Each run starts a session on Talyn Fleet. A session stays in Talyn for review and follow-up.
- Set the Schedule.
- Pick the Repository. A scheduled automation works on one repository.
- Pick the Agent and Model.
- Select Create.
Schedule
| Schedule | Runs |
|---|---|
| Hourly | Every hour, at the minute you pick. |
| Daily | Once a day, at the time you pick. This is the default, at 09:00. |
| Weekdays | Monday to Friday, at the time you pick. |
| Weekly | Once a week, on the day and time you pick. |
| Custom cron | A five-field cron expression, for example 0 */4 * * *. |
Pick a Timezone for the schedule. The editor shows the next runs, so you can check it before you save. Daylight saving changes are handled for you.
If Talyn misses a run during an outage, it runs the scheduled automation once when it can. It does not replay every run it missed.
If the last run is still going
Choose what happens when a run is due and the last one has not finished:
- Skip this run (the default). The skipped run shows in the history.
- Start it anyway.
Internet access
A scheduled automation on Talyn Fleet runs in a sandbox that can reach your repository and its agent, and nothing else. This stops untrusted text from sending your code somewhere.
If the prompt has to call something outside, for example to post to a webhook, choose Allow the internet. Turn it on only for prompts you trust.
MCP servers
Each session gets the tools of your workspace's MCP servers. A scheduled automation cannot choose its own servers.
- Whatever the workspace has on (the default) gives it every server that is on, including servers you connect later.
- Choose for this loop gives it only the servers you pick, or none.
Run now, history and turning off
Select the Run now button on an automation to start a run. Select Show history to see its runs. Each run shows its status and any reason it did not run. A session run includes an Open session link.
Turn a scheduled automation off with its switch. Talyn also turns it off and says why when:
- Its repository or its agent is no longer connected.
- Its schedule has no future runs.
- Five runs in a row failed.
Deleting a scheduled automation removes its history. It does not undo work the automation already did.
Cost
Each run starts a sandbox and uses box-hours. When you are out of box-hours or every box is busy, the run shows Waiting for box-hours or credits or Waiting for a free box, and starts when there is room.