Workflow errors can stop your automations from working properly when required settings are missing or set up incorrectly. ZipLeads spots supported setup issues right in the Workflow Builder and gathers them into a single Resolve Errors sidebar. This helps you fix them before you publish. You can keep saving your progress while errors remain. Issues that block publishing must be fixed before the workflow can go live.

Workflow Error Highlighting and Resolution finds supported setup issues in workflow triggers and actions and makes them easier to find and fix. Visual indicators highlight affected steps on the workflow canvas. The Resolve Errors sidebar brings all detected issues together in one place. This means less time spent opening each step one by one when you're troubleshooting.

ZipLeads can detect setup issues such as missing mandatory fields, disconnected integrations or incomplete settings in supported triggers and actions. Validation also covers settings such as If/Else and Wait actions.

You can review errors directly from the workflow canvas. Any detected issues that block publishing must be fixed before the workflow can be published.

Workflow errors can come from different parts of an automation, including triggers, actions, required fields and integrations. Knowing what caused an error helps you work out which step needs attention and what needs to be fixed.

Examples of supported errors include:

For example, a workflow could flag a missing calendar in an appointment trigger, an empty message body in an SMS action, or a missing subject and body in an email action.

ZipLeads keeps expanding workflow validation, so the errors you see can vary depending on the trigger, action and settings you're using.

Visual error indicators make problems easier to find in larger workflows. Instead of opening every trigger and action to check its settings, you can use the indicators on the canvas to see which steps ZipLeads has flagged.

When ZipLeads detects a supported setup issue, an error indicator appears on the affected step. These indicators match the errors shown in the Resolve Errors sidebar.

Once a supported issue is fixed, ZipLeads automatically removes its error indicator and clears the error from the error list.

Saving and publishing do different jobs in the Workflow Builder. Saving keeps the changes you're making. Publishing decides whether the workflow runs live. Keeping these separate means you can work on an unfinished workflow without fixing every problem in one go.

Manual save and autosave keep your progress even when there are errors on the canvas. You can leave an unfinished workflow, come back later and keep fixing it.

Validation still finds and shows errors while you work. You don't need to fix them before saving your progress.

The Resolve Errors sidebar shows all detected setup issues in the workflow in one place. This makes it easier to see what needs attention and jump straight to the affected trigger or action.

After you select Review issues, the Resolve Errors sidebar shows the affected steps and their errors.

Each applicable error gives you two troubleshooting options:

AI help can explain the error and suggest a fix, but you should still check the workflow settings afterwards to make sure they match what you want the automation to do.

Error visibility controls can make the workflow canvas easier to work on when you don't need error indicators showing. Hiding an indicator only changes whether you can see it. It doesn't fix the problem, so unresolved issues may still need attention before you publish.

​

Fixing setup issues before you publish helps make sure the required settings are in place before contacts enter the automation. The publish check lets you go from the warning straight to the affected steps, without searching through every step yourself.

1: Integration Issues

2: Missing Mandatory Fields

Setup errors and execution errors happen at different stages of an automation. Knowing which type you're dealing with helps you pick the right ZipLeads tool, rather than relying on the pre-publish checks for problems that happen after a workflow starts running.

Note: Fixing pre-publish errors doesn't guarantee every workflow run will succeed. Keep testing and monitoring live workflows where needed.

Q: Can I save a workflow when it still has configuration errors?
Yes. Manual save and autosave keep your progress while errors remain. Publishing is handled separately.

Q: Can I publish a workflow with an unresolved publish-blocking error?
No. When ZipLeads detects an unresolved issue that blocks publishing, the publish is stopped so you can fix it.

Q: Will an already published workflow automatically return to Draft if ZipLeads finds an error?
No. A published workflow doesn't automatically move back to Draft when an error is found.

Q: Does ZipLeads detect every possible workflow problem before publishing?
Don't assume every possible problem will be caught before publishing. Validation covers supported settings and keeps expanding. It's still important to test and monitor workflows after you publish them.

Q: What is the difference between Open step and How to fix?
Open step takes you straight to the affected step so you can change its settings. How to fix gives you AI guidance to understand and fix the error.

Q: What happens after I fix an error?
For supported errors, the error indicator disappears and the error is automatically removed from the error list once the issue is fixed.

Q: Does hiding an error resolve it?
No. Hiding an error only changes whether you can see it. It doesn't fix the underlying setting. If the issue blocks publishing, you still need to fix it.

Q: Are Resolve Errors issues the same as errors shown in Execution Logs?
Not necessarily. Resolve Errors focuses on supported setup problems while you build and publish. Execution Logs and Error Notifications help you troubleshoot problems that happen when workflows run.