Skip to main content
The Schedules runs your skills and automation flows automatically on a recurring schedule: a pipeline report every Monday at 8 AM, an inbox triage every hour, a data sync every 15 minutes. Open it from Schedules in the sidebar.

​
What You Can Schedule

  • Skills: any runnable skill from your Skills
  • Automation flows: any flow from your Automations
Each schedule saves the input parameters for its target, so the run is fully hands-off.

​
Creating a Schedule

1

Click New schedule

In Schedules header, click New schedule.
2

Name it and pick a target

Give the schedule a name, then choose what to run from the tabbed picker (Skills or Flows), with search.
3

Set the timing

Use a preset (every 1/5/15/30 minutes, hourly, daily, weekly, monthly) or write a custom 5-field cron expression. A live preview shows the next three run times so you can confirm the expression does what you intend.
4

Choose a timezone

Schedules run in the timezone you select (for example America/New_York). Daylight saving transitions are handled automatically.
5

Provide inputs

If the skill or flow declares input parameters, a form collects them; otherwise a JSON editor is available. These inputs are used for every run.
6

Save

The schedule activates immediately and the table shows its next run time.
If a run is still going when the next one comes due, the default policy skips the new run (and records it as skipped so you can see it happened). You can change this to allow overlapping runs per schedule.

​
Managing Schedules

The Schedules table shows each job’s name, target, human-readable schedule, status (Active, Paused, or Auto-paused), last run result, and next run time.
  • Pause / Resume: stop and restart a schedule without deleting it
  • Run now: fire the job immediately, outside its schedule
  • Edit: change timing, timezone, or inputs; the next run time recalculates
  • Delete: removes the schedule and its run history (asks for confirmation)
If a schedule fails 10 times in a row, RelayHub auto-pauses it so a broken job does not run forever. Fix the underlying issue, then resume it.

​
Run History

Each schedule keeps a run history: status (success, failed, skipped, missed, or timeout), when it ran, how long it took, whether it was triggered by the schedule or manually, any error message, and links to the outputs it produced. History is retained for 90 days.

​
Limits and Access

  • Schedules is available to all users; each user manages their own schedules. Admins can see everyone’s.
  • Each user can have up to 25 schedules.
  • Run now is rate-limited to 6 per minute.