Waiting for validation segment starts a workflow that checks it and sets its status to Validated.
How it works
The workflow uses two inboxes:- The automated inbox lists every record of the segment. The workflow processes them, nobody takes them.
- The fallback inbox receives a task when a run needs a person: an error, a confirmation or a manual step. Operators work it like any inbox, and the run continues where it stopped.
Validated. When a run ends and its record is still in the segment, the workflow doesn’t start again on that record: fix the workflow or the data.
New records start within 5 minutes by default, up to 20 runs at a time per inbox. Your developers can change this interval in Forest Runtime.
Before you start
To start a workflow on data change, you need:- A segment on the workflow’s collection.
- A Fallback inbox and the On data change trigger turned on, in the workflow’s Triggers section. See Workflow triggers.
- A service account in the inbox’s team. The workflow runs with its permissions, so its role must be able to read the collections of the inbox and of the fallback inbox.
- A fallback inbox that people work from. An automated inbox can’t be the fallback inbox.
- Forest Runtime 1.34.0 or later running on your environment.
Set it up
Only Admins and Process Owners can pick the service account in Runs as.- From the workflow
- From an existing inbox
- In the workflow’s Triggers section, under On data change, click New automatic inbox.
- Pick the Segment, then name the inbox and pick its icon.
- Pick the dispatch rule. The workflow starts the records in this order.
- Pick the service account in Runs as.
- Click Confirm.
Follow the runs
The workflow’s On data change row lists its automated inboxes, with their state and service account. Admins open an automated inbox from the left navbar, where a bolt icon marks it. It opens on its Backlog:
Canceled and Automatically Canceled tasks show through the Backlog filters. Click the refresh icon to update the list.
Operators can’t take, assign or unassign the records of an automated inbox: the workflow holds them.
If more than 100 records are still in the segment after their run, the automation stops starting new runs until your workflow takes them out of the segment. The Backlog header then shows the automation as Stopped, with the reason.
Pause or stop
To pause, open the inbox settings in Layout Editor mode and click Pause in the Process section. No new run starts, and the runs already going finish. Click Resume to start again. A pause applies to production right away. To stop for one inbox, set How it starts to Operators handle the records, no workflow in its Process section and click Save. Operators work the inbox again. The runs already going finish, and records whose run ended while they stayed in the segment go back to operators. To stop for every inbox, turn off On data change in the workflow’s Triggers section. The inboxes stay linked to the workflow, and show as stopped. A workflow’s fallback inbox can’t be deleted while the workflow has an automated trigger turned on. Turn off the triggers or pick another fallback inbox first.Related
Workflow triggers
Manual, webhook, MCP and On data change.
Inbox
How operators process tasks in an inbox.