Skip to main content
A journey cannot run if any required value is unresolved. Reqflo identifies missing values before execution starts and surfaces them so you know exactly what to provide. This happens through the Values panel and, more completely, through the Run check panel.

​
When to use it

You do not configure missing-value detection — it is automatic. You encounter it when:
  • You open a journey and some run inputs or variables have no value and no default.
  • You try to start a run and the Run check blocks it with errors.
  • A collaborator shares a journey that requires values you have not supplied yet.

​
Key concepts

Required vs. optional. A run input or variable can be marked required or optional. Required fields with no resolved value block the run. Optional fields without a value do not block, but may cause step failures if the step expects a non-null value. Resolution check happens before the run. Reqflo validates value resolution when you open the run panel and when you click to start a run. It does not wait for a step to fail at execution time to tell you a value is missing. Errors vs. warnings. In the Run check panel:
  • Errors block the run entirely. A missing required value is always an error.
  • Warnings flag incomplete or risky configuration but may not block the run. For example, an optional value that is unset might surface as a warning if the step uses it in a way that is likely to fail.
Multiple sources can satisfy a required value. A run input might have no default but be satisfied at run time by a case, a preset, or a --set flag. Reqflo evaluates the full resolution chain — if the value can be resolved by any configured source, it is not flagged as missing.

​
How it works

1

Reqflo scans all declared values

When you open the run configuration or click Run check, Reqflo inspects every declared run input, variable, and step output reference in the journey.
2

It checks each value's resolution chain

For each required value, Reqflo checks whether a default, a preset, a case, or another source can supply it. If the chain comes up empty, the value is flagged as missing.
3

Errors are shown in the Run check panel

Open the Run check panel to see a list of errors and warnings. Each missing value is listed with the field name and which step (or the journey itself) requires it. Fix the missing values — by adding a default, supplying a run input, or selecting a case — and re-run the check.

​
Examples

Run check error: missing required run input 
Error: Run input "account_id" is required but has no value.
  → Used by: Step 1 (Get user), field: userId
Fix: Supply a value for account_id in the run panel, use a case that provides it, or add a default value in the Values panel. Run check error: unresolved step output reference 
Error: Step "Get order" references output "order_id" from Step "Create order",
       but "Create order" has no declared output named "order_id".
Fix: Add the order_id output declaration to the “Create order” step. Run check warning: optional value unset 
Warning: Variable "coupon_code" is optional but has no value.
  → Step 3 (Apply discount) may fail if this value is expected.
You can proceed past a warning, but it is worth reviewing.