When to use it
Check this panel before switching to Run mode, especially after making changes to steps, values, or environment configuration. It’s the fastest way to catch configuration issues before they surface as confusing runtime failures.Key concepts
- Errors — issues that prevent the journey from running at all. Reqflo will not execute a journey with unresolved errors. You must fix all errors before a run can start.
- Warnings — issues that don’t block execution but indicate risk: incomplete setup, potentially invalid configuration, or behavior that might cause the run to fail unpredictably. Warnings are worth reviewing even if they don’t stop you.
- Checks — the specific validations the panel runs. These cover the most common reasons journeys fail before they’ve even started.
How it works
Open the Run check panel from the Build-mode panel rail. Reqflo evaluates the journey and lists any issues found, grouped by severity. What the panel checks:| Check | Severity |
|---|---|
| Missing required values — a step needs a value with no source configured | Error |
| Invalid references — a value references a step output, variable, or field that doesn’t exist | Error |
| Missing secrets — a secret reference names a secret that isn’t available in the current context | Error |
| Incompatible environment — the selected environment doesn’t support a step’s requirements | Error |
| Unresolved step outputs — a step references the output of a previous step, but that step’s output shape is unknown | Warning |
| Invalid step configuration — a step has misconfigured parameters (e.g., a malformed URL template) | Error |
Run check validates the journey’s static configuration. Some issues — like a secret that exists in the store but has the wrong value — can only be caught at runtime.
Examples
Scenario: Missing value You added a new step that usesaccount_id as a run input, but forgot to configure it in the Values panel. The Run check panel shows:
Error: Missing value — account_id on step “Fetch account” has no source configured.
Scenario: Broken step-output reference
Step 3 references steps.step-1.body.order_id, but step 1 was renamed to create-order. The Run check panel shows:
Error: Invalid reference — Step “Confirm order” references output from step step-1, which does not exist.
Scenario: Warning on unresolved output shape
A step’s output shape depends on a response that hasn’t been run yet, so Reqflo can’t confirm the referenced path exists. The Run check panel shows:
Warning: Unresolved step output — steps.create-order.body.metadata.transaction_id — output shape not yet known. The reference may be valid; run the journey to confirm.
Related pages
Values panel
Configure value sources to resolve missing-value errors.
Missing values
How missing-value detection works across the journey.
Step outputs
How step outputs are referenced and resolved.
Secrets
How secret references work and where values are resolved.