Schedule an Agent in Pylon
Run a Pylon Agent on a cadence - add a Schedule trigger, pick hourly, daily, weekly, monthly, or custom cron timing in UTC, and enable the trigger safely.
What you’ll accomplish
Section titled “What you’ll accomplish”Your Agent will run itself on a cadence you set - hourly to monthly, or any custom cron expression - with the schedule readable in plain language before you turn it on.
What you’ll need
Section titled “What you’ll need”- An Agent (see Create your first Agent)
- The cadence you want, in UTC - schedules have no timezone picker, so convert your local time first
1. Add a Schedule trigger
Section titled “1. Add a Schedule trigger”On the agent’s editor, open the Triggers tab and select Add a trigger. Pick Schedule (“Run on a cadence you set with a cron expression.”). Each trigger type can be added once per agent; the others are Manual, GitHub webhook, and Agent-to-agent.
2. Pick the frequency
Section titled “2. Pick the frequency”The Frequency selector adjusts the fields:
| Frequency | You set |
|---|---|
| Hourly | At minute (0-59) |
| Daily | At time (UTC) |
| Weekly | On days (Su-Sa toggles, keep at least one) + At time (UTC) |
| Monthly | Day of month (1-31) + At time (UTC) |
| Custom (cron) | A Cron expression, for example */15 9-17 * * 1-5 |
A new schedule starts as every day at 09:00 UTC until you change it.
3. Read the preview back
Section titled “3. Read the preview back”Under the controls, the schedule renders in plain language - “At 09:00 AM, only on Monday” - always suffixed “Interpreted in UTC.” If the preview doesn’t say what you meant, adjust before enabling.
4. Enable it
Section titled “4. Enable it”New Schedule triggers are added disabled so nothing fires half-configured. Flip the Enabled switch, then Save - and Publish if the agent is still a Draft, since triggers run the published revision.
You’ll see scheduled runs appear in Monitor → Activity, and cadence statistics under Insights → Analytics on the Triggers tab.
If it didn’t work
Section titled “If it didn’t work”- The run fired at the wrong hour. Schedules are UTC - re-check the conversion from your local timezone.
- Nothing fires. Confirm the trigger’s Enabled switch is on and the agent is Published (Active), not Draft.
- My cron expression got moved to Custom. Expressions with steps, ranges, or named days display under Custom (cron) and are preserved exactly as written.
Next steps
Section titled “Next steps”- Agent configuration reference - Limits keep scheduled runs inside guardrails (steps, tokens, spend, idle time)