Schedules
Schedules in the sidebar (/scheduler) lists every schedule in the workspace: what it is for, how often it runs, in which timezone, how its last run went and when it fires next. In FluidGrids a schedule is created by giving a workflow a Schedule Trigger and activating it; this screen is where you see all of them together and operate them.
The screen is the platform's shared scheduler module, so the same page exists in other Burdenoff products. What differs per product is what a schedule is for: in FluidGrids that is a workflow, and the screen links to it.
Upcoming executions
The strip at the top shows the next 12 hours across all schedules on a timeline, in your own timezone. Each chip names the workflow and the time it will fire; hover for the time in the schedule's own timezone, click to open the workflow. Overlapping fires stack on extra rows; when more fires fall in the window than fit, the strip says how many more there are. The strip refreshes itself every few minutes, or on Refresh.
The times come from the scheduler itself (the same calculation that produces the Next runs preview in the Schedule Trigger node), so the strip and the node agree.
The table
| Column | What it shows |
|---|---|
| Schedule | The workflow the schedule belongs to (a link to the builder) and the rule's description. |
| Runs | The rule in words — "Every minute", "Daily at 6:00 AM", "Every 2 weeks on Monday and Wednesday at 8:15 AM"; the raw cron expression or recurrence rule is shown underneath and in the tooltip. |
| Timezone | The zone the rule is evaluated in, with its current abbreviation (Asia/Kolkata, IST). |
| Last run | When the schedule last fired, in its own timezone, and how it went: Success, Failed or Running. The outcome links to the run in Runs. Never means it has not fired yet. |
| Next run | How far away the next fire is ("in 8h 37m") and the clock time in the schedule's timezone. Paused and draft schedules show "—". |
| State | Active (the scheduler will fire it), Running, Paused, Draft (registered but not armed, for a workflow that is not active), Failed, Completed, Disabled. |
Search by workflow name, filter by State or by Timezone, and page through with the arrows at the bottom. Click a row to open the schedule's detail page, which shows its full configuration and execution history.
Operating a schedule
Each row has a menu with:
- Pause / Resume — stop or restart the schedule without touching the workflow. A paused schedule stays paused when the workflow is saved again; activating a version of the workflow arms all of its schedules again.
- Run now — fire the schedule once, immediately. The run is attributed to the person who set up the schedule, exactly like a scheduled fire; it does not move the next planned time.
- Open <workflow> — open the workflow in the builder.
- View last run / Execution history — the last run in Runs, or the scheduler's execution history for this schedule.
A schedule that belongs to a workflow is edited or removed in the workflow: change the rule in the Schedule Trigger node and save, or delete the node. Changing a rule keeps the same schedule (its history and its paused or active state); the next run is recomputed. The detail page says who manages the schedule and offers no delete for it.
Who can see it
The entry appears for members who can read scheduled jobs (the Automation Owner, Automation Lead, Workflow Designer, Run Operator and Automation Auditor roles). Pause, resume and run now follow the scheduler's own permissions, so a role that can only view sees the table without the actions.
Troubleshooting
- A schedule is missing — only the Active version's rules are registered. Check the workflow's Versions panel; a Draft workflow has no schedules here.
- Next run says "—" — the schedule is paused or not armed. Resume it here, or activate the workflow.
- The last run failed — open it from the Last run column; the run's logs show the failing node. The schedule keeps firing on its timetable.
- Nothing in the next 12 hours — none of the active schedules fire in that window; the table's Next run column shows when they will.