Reqflo surfaces errors at two stages: during Run check (before execution starts) and at runtime (during step execution). Run check errors block the run entirely; runtime errors stop execution at the failing step and are captured in run output.
Run check errors
The Run check panel shows what must be fixed before a journey can run. Errors block the run; warnings flag risk or incomplete setup without necessarily blocking.
| Error | Cause | Fix |
|---|
| Missing required value | A required run input or variable has no value from any source (no run input, no case, no preset, no hard-coded value). | Supply the value via a case, a --set flag, a variable preset, or a hard-coded value. See Value resolution order. |
| Invalid reference | A template expression references a field that does not exist — e.g. {{ inputs.nonexistent }} or a misspelled variable name. | Check the expression for typos and confirm the input or variable is declared in the Values panel. |
| Missing secret | A secret reference points to a secret name that cannot be found in the secrets store for the selected execution mode. | Verify the secret exists in Admin → Secrets (for cloud runs) or is set in your local environment (for local runs). |
| Incompatible environment | The selected environment is missing required configuration for this journey (e.g. a required base URL or service-level value is not defined for that environment). | Update the environment configuration in Admin → Service environments or select a compatible environment. |
| Unresolved step output | A step references an output from a previous step that cannot be resolved — either because the source step doesn’t exist, the path is wrong, or the referenced step precedes the current step incorrectly. | Confirm the source step ID and output path exist. Step outputs are only available from steps that run before the referencing step. |
| Invalid step configuration | A step is misconfigured — for example, a required template field is missing, the request template cannot be found, or a step field contains an invalid value. | Open the step in Build mode and review the configuration. The Run check panel will indicate which step and field is affected. |
Runtime errors
These errors occur during journey execution. They appear in run output alongside the failing step.
| Error | Cause | Fix |
|---|
| HTTP request failed | The request could not be completed — network error, DNS failure, connection refused, or timeout. | Check that the target service is reachable from the execution environment. For cloud runs, verify the environment base URL and network configuration. |
| Assertion failed | A step response did not match one or more assertions. | Review the assertion and the actual response in run output. Adjust the assertion or investigate why the API returned an unexpected result. |
| Step output extraction failed | The expression used to extract a value from a step’s response (e.g. a JSONPath) did not match anything in the response. | Inspect the actual response body in run output and verify the JSONPath expression is correct. |
| Secret resolution failed at runtime | A secret reference could not be resolved when the step executed. | Confirm the secret is configured in the correct secrets store for the active execution mode (cloud vs. local). |
| Run aborted | The run was manually abandoned (e.g. via Debug mode) or timed out. | Not an error in the journey itself. Retry or investigate the reason for abandonment. |
Warnings vs. errors
| Severity | Behavior |
|---|
| Error | Blocks the run from starting (Run check) or stops execution at the failing step (runtime). |
| Warning | Surfaces a risk or incomplete configuration but does not block the run. Review warnings before running in production. |
The Run check panel summarizes all errors and warnings in one place before you run. Fix errors first; then decide whether warnings are acceptable for your use case.
Related pages
