Publish and troubleshoot Logic Flows

Publish a saved version of your flow, then activate it for its assigned WhatsApp numbers. Later draft edits do not change that published version. If publication or activation fails, use the displayed issue to find the setting that needs attention.

When resources cannot be loaded

The editor may show: Flow resources could not be loaded. Publishing is blocked so missing resources are not misreported. This means the draft opened, but one or more supporting lists did not load reliably.

1. Select Retry in the affected section.
2. Confirm the selected WhatsApp number is connected and available to your role.
3. Check referenced templates, forms, teammates, sub-flows, and integration actions.
4. If the same message remains, leave publishing blocked and contact support with the flow name and time of the retry.

Do not delete nodes just to remove the warning. The resource may still exist while its current status cannot be verified.

When validation fails

Open each reported node and correct its required fields, connection, or resource. Common causes include an unconnected branch, a missing fallback, an unavailable template, a form without a valid reference, or a sub-flow without a selected published version.

Run validation again after the final edit. The absence of a canvas warning is not a substitute for the publish validation.

Replace the active version

Edit the draft, validate it, and publish a new version. Then activate that version through the available control. Existing in-flight conversations may finish under the version that admitted them, so avoid changing a shared resource in a way that breaks an earlier path.

Recover a customer safely

If a path stops after an external action or resource error, use Inbox to read the message history and assign the conversation. Add an internal note describing the failed step before replying. This preserves context for the next teammate and avoids making the customer repeat information.

If a published flow receives no messages

Publishing alone does not activate the flow. Check Settings > Flow settings, its WhatsApp Business Account, Assigned numbers, and Active state. Save the account and number configuration with Active off, publish that exact configuration, then turn Active on and save. Confirm the actual trigger and number handling mode with a permitted inbound test. See the activation sequence.

If the binding and activation are correct:

• Open Settings > Developer > API keys and confirm Logic Flow handling for that number. Use Logic Flow switches it from Developer API handling.
• Check the trigger condition. Conversation entry can apply only to a first-ever contact or a new session; another message inside the existing session may not trigger it.
• Check human ownership. Activating a flow does not take a conversation away from its human owner.
• Resolve conflicting-trigger warnings rather than expecting two flows to answer. Fallback is a trigger, not a separate default-flow setting.

Next: Work in Inbox or create an Automation flow.