Running Workflows & Scheduling
When a trigger fires and the filter matches, Full Fabric creates a workflow for the person: their own copy of the steps, which runs in the background. This page covers how those workflows move, when their steps run, and what staff can do with them.
Workflow States
| State | Meaning |
|---|---|
| Created | The workflow has just been created; it becomes idle at once |
| Idle | Waiting for its next step to be due, either straight away or after a Wait step |
| Running | Its steps are running now |
| Paused | On hold. It runs no steps until it is unpaused, or its template is resumed with Also resume paused workflows |
| Done | Every step has run |
| Exited | It stopped early, because an exit condition was met or a staff member selected Exit |
| Error | A step failed. The remaining steps do not run |
Steps run one after the other without a pause until the workflow reaches a Wait step or the end. A failed step is not retried: the workflow stays in Error, and the error message is shown on the failed step.
The Runs List
Running workflows are listed:
- on the Runs tab of the Workflows page, opened from the settings (gear) menu;
- on the Workflows tab of Settings → Automation & AI → Workflow rules;
- for one template, on its Enrolments page (View enrolments);
- for one person, on the Workflows tab of their profile, for administrators.
| Column | Shows |
|---|---|
| Target | The person the workflow is for, or System for workflows not tied to a person |
| Trigger | What started it |
| State | The state badge |
| Actions | Its steps, with the failed one marked and its error shown on hover |
| First run | When the workflow was created |
| Last run | When a step last ran |
| Next run | When the next step is due |
Filters: Target (All workflows, Profile workflows, System workflows) and States (Idle, Running, Paused, Done, Error).
| Row action | Offered when | Effect |
|---|---|---|
| Run | Idle and due | Runs the next steps now |
| Pause | Idle | Puts the workflow on hold |
| Unpause | Paused | Puts it back in the queue |
| Exit | Not done and not in error | Ends the workflow for good. There is no confirmation in the runs list; the profile tab asks first |
Wait Steps
A Wait step holds the workflow until a moment, then lets it continue. Choose the Wait timing:
| Wait timing | Fields | Continues |
|---|---|---|
| Wait duration | Days, Hours, Minutes | That long after the step is reached |
| Fixed date | Wait until, a date and a time | At that moment. A date already past lets the workflow continue at once |
| Relative date | Days before and Date: Before class start date, or Before class application close date | That many days before the class date. Lifecycle workflows only |
A relative wait reads the class date when the step is reached. When the class has no such date, or the moment has already passed, the workflow continues at once. Workflows set up from application templates can also wait relative to the application close date.
Note: A Wait step does not re-check the filter. People who no longer match after the wait still get the following steps, unless an exit condition removed them.
Scheduling
Full Fabric checks continuously for workflows whose next step is due and runs them, in batches. A step that is due runs shortly after; a long backlog is worked through batch by batch.
Scheduled system workflows run on three clocks:
| Trigger | Runs |
|---|---|
| Minute schedule | Every minute |
| Hourly schedule | Once an hour, at 40 minutes past, server time |
| Daily schedule | Once a day, at 05:00 server time |
Segment workflows are checked on the same continuous cycle (see Segment Triggers). Task reminders follow their own schedule, described in Tasks.
The Action Log
View log on a template opens its Log: one entry per logged action, with the Action type, the Payload the action received or sent, and when it was Created at. Steps that send email, call webhooks, tag people, transition journeys, make offers or create records from field values write to it. Use it to see exactly what a webhook received and answered, or why a step did nothing.
Who Gets a Workflow
- A person can be in the same workflow several times when its trigger fires several times, for example one per form submission.
- An exit condition is checked against each new event about the person, once the first step has started.
- A workflow keeps the steps it had when it was created. Editing or deleting the template does not change the workflows already running; deleting pauses them.