# What does it mean when a workflow run is waiting for input?

Canonical URL: https://help.iagenify.com/faqs/workflows/what-does-it-mean-when-a-workflow-run-is-waiting-for-input

[← Back to Workflows FAQs](https://help.iagenify.com/faqs/workflows)

HELP CENTER · FAQ Workflows 2 min read
# What does it mean when a workflow run is waiting for input?
A waiting run is paused at a defined point rather than failing. The run history can show which step needs input, so you can supply the missing decision or value and continue from that point.
IaGenify
Workflows

## Inspect what the step is asking for
Open the run details and read the waiting step's title and context. Determine whether it expects a human decision, a value from an earlier step, or confirmation of an action. Do not guess at an input shape if the workflow has not made it clear; check the step configuration or revise its instructions first.
Compare the prompt with the original event and the data already available in the run. If a person must decide, provide the choice deliberately and preserve any context that informed it. If a value is missing, identify the source step and correct the mapping rather than entering a placeholder that could affect later actions.
## Resume and confirm the downstream result
Once you have the required input, resume the waiting run at the appropriate step. Review the next step's output and check that the workflow followed the intended branch. If the supplied value changes what the workflow does, confirm the resulting action before allowing it to affect external services or stored data.
A waiting state can be part of a deliberate review process, especially when a workflow should pause for a person before continuing. If the run waits unexpectedly, adjust the step or its inputs and test again. Keeping the decision point explicit makes the workflow easier to supervise and the run history easier to understand. [← Back to Workflows FAQs](https://help.iagenify.com/faqs/workflows)