Schedules

Open in product: preshos.com/automations/schedules

Schedules is the second half of Connect in the Automations module: the recurring runs that fire without a live session behind them. New scheduling goes through Inngest via function-catalog; connector-sync-runner stays dead and is not revived for new syncs. The module around this page is Automations.

• The left rail splits the module three ways: Build (Workflows), Connect (Connectors, Schedules), Observe (Activity, Runtime, Triggers, Logs). Schedules sits in Connect beside the installs its rows run against.
• Each row names the schedule with its agent, environment, owner, cron expression, and next run. Search, Next-Run sort, Columns, and Filters narrow the list; New Schedule starts one.
• One schedule owns one recurrence. A schedule that means three recurrences forces every observer to guess which firing did what.
• This surface is connector and workflow timing, not working hours. People hours, time off, and user assignments live under Work Schedules; the two never substitute for each other.

Agent Ops schedules vs. module schedules

The table above is the Automations module’s schedule list at /automations/schedules. Agent Ops carries a separate Scheduled surface for agent schedules and heartbeats, described under Automations: it defaults to schedules created by the current user (“My automations”), edits schedules and heartbeats in native detail editors, keeps agent-record tabs agent-scoped, and can show authorized multi-owner rows on the global views. When you cannot find a schedule, check which surface you are on before concluding it is missing.

What next

• Automations: the module this schedule list belongs to, including the Agent Ops Scheduled (“My automations”) surface.
• Connectors: the installs these schedules run against.
• Automation activity: where each firing lands in the run record.