WAX provides an activity log, called Activities, that lets you track every contact that entered a flow — whether each step was completed as expected, and if not, what happened and how to fix it.
Where to find Flow Activities?
In a draft campaign (not yet sent)
Open the campaign from your campaign list in WAX
Click "Show activity" in the top bar, available at step 1 "Content" only
In a completed campaign (already sent)
Open the campaign from your campaign list in WAX
Click the "Activity" tab in the top bar
In an automation
Open the automation from your automation list in WAX
Click the "Activity" tab in the top bar
How to read the Activities page?
The activity list
The panel displays all contacts that entered the flow, with a timestamp and status. You can:
Search for a contact by phone number or name to check whether they were included in the flow
Filter by error type to quickly identify problematic executions
Filter by time period to narrow the view to a specific window
Activity detail
Clicking on a contact in the list highlights their path through the flow, node by node. You can see at a glance where the contact went, where they stopped, and why.
For example here, the contact didn't click any CTA, the flow simply didn't continue for them.
For each activity, and for certain nodes, you'll have access to:
Flow payload: the technical data passed at the start of the execution (e.g.
reference_id, ...)Variables: the dynamic values used during a node's execution (e.g. the contact's first name, message content)
Contact attributes: the attributes known about the contact at the time the node ran (e.g.
whatsapp_opt_in_status,language, ...)
💡 This data is especially useful for understanding why a contact took an unexpected path, for instance, if they were excluded from a node due to a missing attribute. |
Failed executions
When a node could not be executed, the activity is marked Error. Clicking on it gives you the full detail: which node failed, the cause, and the available actions.
In some cases, you can trigger a retry directly from the interface to retroactively fix a past execution, without having to re-send the entire campaign/automation. In other cases, WAX may automatically retry when possible.
Either way, the retry count will not be 0. The retry count indicates how many attempts have been made to resolve the failed node.
ℹ️ It is not possible to cancel an activity that is in progress or already completed. |
How to resolve the most common errors?
Titre de l'erreur | Description de l'erreur | Actions |
Meta encoutered a payment issue on your account | There is a payment issue on your Meta account linked to your WhatsApp Business account. Messages cannot be sent until this is resolved. | 1. Go to your Meta Business Manager and either settle your outstanding balance or set a new default payment method. 2. Once fixed, come back here and retry the failed activities. |
Meta blocked this message to protect WhatsApp ecosystem health | This message wasn't delivered to improve user experience by capping the number of marketing messages a person can receive within a certain time. This is unrelated to your content or your WAX setup. | You can retry this message after 24 hours. No changes are needed on your end. |
Meta blocked this message to protect WhatsApp ecosystem health in the USA | Marketing template to US contacts are not allowed at the moment. This is unrelated to your content or your WAX setup. | You can add a condition for numbers starting with the prefix +1 (USA) and send a SMS instead. |
Meta blocked this message because the conversation window expired | More than 24 hours have passed since this contact last interacted with your WhatsApp number. Meta no longer allows Reply messages outside this window. | Send an approved message template to re-engage this contact directly from WAX Inbox or through your customer service integration. |
Your WhatsApp number is no longer registered | The WhatsApp Business number linked to your account is no longer registered on Meta. This is likely because the number was removed or disconnected. | Reach out to your CSM. |
An undefined error has occurred | This error is unknown and has to be investigated by WAX's team. | Reach out to WAX. |
Your media file could not be uploaded | WAX encountered an issue uploading the media file attached to this message. This is usually a temporary error. We're already processing the file in the background and will retry automatically. | No action needed. This node will retry automatically. If the issue persists, check that your media file is valid and accessible. |
Media URL could not be resolved | The variable used in the media URL returned an empty or invalid value, and no default media was set as fallback. The message could not be sent. | Check that the variable redirects to a valid, publicly accessible URL for all your contacts. If some contacts may not have this value, set a default media file on this template to avoid future failures. |
Webhook returned an error | The webhook responded with a 4xx or 5xx status code, indicating an issue with your endpoint configuration or server. This is not related to WAX. | Check your webhook URL and server logs to identify the issue, then retry this execution once it's resolved. |