Control when a step runs and proceeds
Some workflow steps should not run for every work item. Others should run, but should not proceed to the next step until the work item is in a certain state.
Workflow Options on a step lets you declare both rules with the same condition builder used elsewhere in Thunk (for example in tests):
Step Filter Condition — only run this step if the work item meets the condition; otherwise proceed to the next step.
Step Finish Condition — only proceed to the next step if the work item meets the condition; otherwise do not continue.
Thunk checks these conditions directly (not AI judgment in directions). They are different from a tool’s Availability condition, which only limits when a tool can be used inside a step that still runs.
Where to find it
Open your thunk and select a workflow step.
From a work item, open the step’s Settings tab. (When authoring the workflow plan, open the step’s details panel.)
Expand Workflow Options.
Step Filter Condition
Use this when the decision is based on work-item property values you can express as a filter — for example:
Only process work items where
Amountis greater than a thresholdSkip a step when a required field is empty
Only run a follow-up step when a prior-step result field has a specific value
Prefer this over writing “skip this step if …” in directions when you want a deterministic skip (same property values → same skip/run behavior, no AI call on skipped work items).
Set, edit, or clear a filter condition
Conditions can use any property on the work item (including columns that are not bound as inputs for this step). If the work item has no properties yet, the panel shows that no properties are available.
When properties are available:
Under Step Filter Condition, choose Add Condition.
In the dialog, pick one or more column / operator / value rows (combined with and / or as shown).
Choose Save.
The panel shows a short summary of the saved condition. Use Edit Condition to change it, or Clear to remove it so every work item runs the step again.
What happens when a work item is skipped
For a work item that does not meet the filter condition:
The step is marked done without agent work for that work item
The work item advances to the next step in the plan
The step’s chat records: Step skipped because the filter condition did not pass.
When a condition is set and the work item does match, the step runs normally. The step chat may also note: Filter condition passed; running this step.
Skip this step for test work items
Below the filter-condition controls is a separate toggle: Skip this step for test work items.
Turn this on when a step should not run during automated test re-runs — typically side-effecting steps such as sending email or writing to an external system. On a re-run of a work item that carries test assertions, that step is skipped and the work item advances; the step chat records: Step skipped because this is a test row. (“Test row” here means a test work item.)
You can use a filter condition and the test toggle on the same step. The test skip applies when the work item is a test work item being re-run; the filter applies to whether the work item’s properties match your condition.
Tip: on a test re-run, the step you start from may still execute; the toggle is most useful for later steps in the plan that should stay quiet under test.
Step Finish Condition
Use this when the step should run, but the workflow should not proceed to the next step until the work item reaches a required state — for example, only proceed when ReviewState is Complete.
This uses the same Add Condition dialog as the filter condition. It is a hard stop on automatic proceed (similar in spirit to requiring a human to finish the step). A person can still finish the step manually from the step controls.
Set, edit, or clear a finish condition
Under Step Finish Condition, choose Add Condition.
Build the condition the same way as a filter condition, then Save.
What happens when the agent tries to proceed
When the agent is ready to finish the step and move on:
If the work item matches, the workflow can proceed automatically when a human is not required to finish the step. The agent’s conclude message includes: Finished step because filter conditions were met, with a link that opens Workflow Options → Step Finish Condition.
If the work item does not match, the step stays open. The conclude message includes: Did not finish step because filter conditions were not met, with the same link to Step Finish Condition. Finish the step manually when ready, or let a later run try again once the data matches.
Tips and common mix-ups
You can filter on any work-item column — you do not need to bind it as an input for this step first.
A Step Filter Condition skips the whole step. A tool Availability condition only controls whether that tool is offered while the step still runs.
Writing “skip this step if …” or “only proceed when …” in directions asks the AI to decide; Workflow Options decides for you.
The filter condition is checked when the work item enters the step. The finish condition is checked when the agent tries to finish the step and move on.
Clearing a condition restores the default (every work item runs; the workflow can proceed when this step’s work is done).