Stop Block
Stop terminates the current Flow path. It does not change the page, create variables, or run downstream Blocks.
At a glance
What it does
Stop is an explicit endpoint for a Flow path. When execution reaches it, Scrapeer treats that path as complete.
Use it after a condition, fallback, or optional branch when there is nothing else to do.
Use it when
- End a branch after a condition chooses a complete path.
- Stop after logging or saving enough information.
- Make a Flow visually clear by showing where a path ends.
Do not use it when
- Another Block still needs to run after this point.
- You want to recover from an error; connect an error handle to a fallback instead.
- You only need to pause before continuing; use Wait.
Settings
Stop has no user-configurable settings.
No settings
Required: No- Variables
- No
- Description
- The Block ends the path as soon as it runs.
Outputs
Stop does not produce a reusable variable.
completedruntime stateThe runtime records that the Flow path reached an endpoint.
Example Flow
Use Stop at the end of a branch when the branch should not reconnect to the main path.
- Route a branch with Conditional.
- Run any final action for that branch.
- End that path with Stop.
Errors and fixes
Start with symptoms visible in the editor or Inspector, then check the earliest Block that produced the wrong page state, variable, or output.
Later Blocks do not run.
- Check
- Check whether the path reaches Stop before those Blocks.
- Fix
- Move Stop to the true endpoint or reconnect the path before Stop.
A branch looks unfinished.
- Check
- Check whether the path intentionally ends there.
- Fix
- Add Stop when the branch is meant to complete without more actions.
Local and cloud runs
Local and cloud runtimes both treat Stop as an intentional end of execution for the current path.