Pause and resume nodes
Temporarily skip a step while preserving its configuration, and understand what happens to its outputs and branches.
- TRIGGERTrigger
- STEP 01Paused node is skipped
- STEP 02Continue on the first branch
Plan availability #
| Feature | Free | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Active workflows | 3 | 10 | 45 | Unlimited |
Allowances follow the published Chatigram pricing page. Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.
What pausing does #
Use Pause node to keep a node in the workflow while skipping its work in new runs after you save. Its configuration and connections stay in place. This is useful when temporarily bypassing an optional enrichment step or isolating a problem.
Runs already in progress are not affected by the saved pause change.
Understand the effects #
| Part of the workflow | While the node is paused |
|---|---|
| The node’s action | Skipped in new runs using the saved configuration |
| Its variables | Still selectable, but their values are empty |
| A node with multiple branches | Continues along the first branch without evaluating its normal logic |
| Configuration and connections | Preserved |
| Existing runs | Unaffected by this change |
Pausing a condition or router can change the meaning of the flow because the first branch is taken. Check what that branch does before saving.
Pause a node #
- Open the workflow editor and select the intended node.
- Use Pause node.
- Read the confirmation, especially if the node has several branches.
- Check later steps for variables supplied by this node.
- Save, then test a new run.
Resume a node #
Use the resume control on the paused node, review the confirmation, and save. New runs execute the node normally again; its outputs receive values from execution and its branches follow their configured logic.
Example: bypass enrichment #
Suppose your flow receives a customer message, calls an optional lookup, and then sends a reply. If you pause the lookup, the reply must still make sense when the lookup’s variables are empty. Use a default response or a condition to handle missing information.
For a larger investigation, copy the workflow and test the copy rather than changing a live customer flow repeatedly.