When to use review
- You want a human gate before delivering results to a downstream system. Set Pause mode to
Always. - You only want humans involved on uncertain runs. Pair
LowConfidencewith a confidence threshold, orUnverified Fieldswith extract’s Field confidence toggle. - You want a fallback path when validation fails on the
Warnaction: route the warned run into review for correction. - You want to gate the run on specific cross-field rules. Add an upstream Validation node and set this node’s pause mode to
Validation failures. Only the runs whose rules recorded a failing field path pause. - You want to catch numeric disagreements between two sources. Add an upstream Reconcile node and set this node’s pause mode to
Reconcile mismatch. Only the runs whose two sources disagree pause. - Skip review when an automated validation check or transform can fix the data deterministically. Reserve human time for cases that genuinely need judgment.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Pause mode | select | Yes | Always pauses every run. LowConfidence pauses only when the confidence score is below the threshold. Unverified Fields pauses when the upstream Extract node produced one or more unverified fields. Validation failures pauses whenever an upstream Validation node is present and consumes the failing field paths recorded by that node’s Warn action (when its rules can attribute them). Reconcile mismatch pauses when an upstream Reconcile node found an out-of-tolerance difference between its two sources. The editor hides the modes whose upstream prerequisites are missing |
| Confidence Threshold | number (0–1) | When mode is LowConfidence | Minimum confidence score. Runs below this threshold are paused for review. Defaults to 0.85 when the LowConfidence pause mode is selected |
| Reviewer Instructions | string | No | Instructions displayed to the reviewer in the review queue |
| Auto-assign Reviewer | select | No | Who the created review task is assigned to. Defaults to “Anyone can claim”, which sends the task to the general queue so any reviewer can claim it. When you choose a teammate, the review task is pre-assigned to that person, who can still be reassigned later. Only active org members appear in the list |
Inputs and outputs
Allowed inputs: Extract, transform, route, merge, parse, validation. Maximum one input connection. Output: Approved (and possibly edited) data, passed to the next connected node.Common pitfalls
Pause mode = Always on a high-volume pipeline
Pause mode = Always on a high-volume pipeline
Always pauses every run. On a busy pipeline this floods the review queue and stalls throughput. Use LowConfidence or Unverified Fields to gate only the runs that need attention.Unverified Fields without Field confidence enabled upstream
Unverified Fields without Field confidence enabled upstream
Unverified Fields mode only triggers when the upstream extract node has Field confidence enabled (Engine 1 only). Without it, no fields are ever marked unverified and the review node never pauses.Validation failures mode without a validation node upstream
Validation failures mode without a validation node upstream
Validation failures activates whenever an upstream Validation node is present and consumes the failing field paths recorded by that node’s Warn action (when its rules can attribute them). The editor hides this pause mode when no Validation predecessor is connected.Reconcile mismatch mode without a reconcile node upstream
Reconcile mismatch mode without a reconcile node upstream
Reconcile mismatch mode requires an upstream Reconcile node. The editor hides this pause mode when no Reconcile predecessor is connected.Min confidence set without testing the score distribution
Min confidence set without testing the score distribution
The right threshold depends on what your runs actually score. Set
Min confidence after you’ve seen real distributions for your documents; defaults that look reasonable can pause everything or nothing.No fallback when reviewers reject a run
No fallback when reviewers reject a run
A reviewer can mark a run failed. Make sure the failure path is intentional: either delete the document, route to a fallback pipeline, or notify a system. Don’t let rejections sit silently.
Related
Human review guide
Set up and manage human review workflows
Review queue
Learn how the review queue works
Extract action
Extract data before review
Transform action
Transform data after review
Reconcile action
Compare two sources before review