Disabling an action can skip that node while later active actions still execute. Review the complete path before using it during maintenance.
Before you beginConfirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.
Step by step
- Locate the workflow and identify the precise action you intend to suspend.
- Read the actions before and after it, including branches and customer messages.
- Decide whether skipping only this action is appropriate. If all activity must stop, ask the workflow owner for the supported broader stop procedure.
- Make an authorized draft change and review how the node is shown as disabled.
- Use a controlled contact to inspect the execution log. Confirm the action is skipped and observe what runs next.
- Document the change, its reason and re-enable conditions. Review the path again before resuming the action.
Expected result
The team understands which node is skipped and which downstream work can still run.
Troubleshooting
- If later messages continue, that can be expected behavior rather than a failed disable.
- Check logs for skipped versus failed actions; they mean different things.
- Avoid changing several nodes at once when diagnosing a single action.
Supporting documentation
These links open the provider’s documentation. Availability and permissions depend on your account.
More guides
Create and verify a contactKeep a single useful customer record, check the business context, and confirm your changes saved.
Review and respond to a conversationFind the right thread, review its history, and check the channel and recipient before responding.
Check a website lead form before launchFollow a controlled submission from the public form to the correct contact and follow-up process.
Prepare an authorized private integrationDefine the business, owner and permissions before an administrator grants a developer access.