WhatsApp services
WhatsApp operations and delivery status
Relate conversations, message states, workflow executions, analytics, logs, and account usage.
Business usersAutomation buildersAdministratorsBeginnerAvailable
What this guide covers
- Operational views answer different questions: Chat shows conversations, Analytics shows aggregate workflow performance, and Developer logs show message and event records.
- Prerequisites: A message, workflow execution, or event to inspect.
- Result: You can distinguish accepted, processing, completed, failed, and delivered evidence for the operation.
- Limit: No single UI combines every no-code and Developer Platform record into one export.
What this is and when to use it
Operational views answer different questions: Chat shows conversations, Analytics shows aggregate workflow performance, and Developer logs show message and event records.
| Use it when | Expected outcome |
|---|---|
You need to confirm a message outcome. | You can distinguish accepted, processing, completed, failed, and delivered evidence for the operation. |
You need to investigate a repeated workflow or delivery problem. | You can distinguish accepted, processing, completed, failed, and delivered evidence for the operation. |
Before you begin
- A message, workflow execution, or event to inspect.
Prerequisites
A message, workflow execution, or event to inspect.
Complete the task
- Open Chat to confirm conversation-level inbound and outbound activity.
- Open Agent Analytics for execution counts, failures, cost, and node patterns.
- For Developer Platform sends, use Messages, Events, Deliveries, and Usage.
- Correlate stable Yanola IDs rather than relying only on timestamps.
Confirm it worked
- You can distinguish accepted, processing, completed, failed, and delivered evidence for the operation.
Common problems
| Symptom | What to check |
|---|---|
A 202 response is treated as delivery | 202 means accepted, not final WhatsApp delivery; wait for status evidence. |
Analytics and Balance differ | Analytics cost is scoped to the selected executions; Balance is shared at account level. |
Current limitations
No single UI combines every no-code and Developer Platform record into one export.
Product boundary
No single UI combines every no-code and Developer Platform record into one export.
Where to go next
Related documentation
Messages, events, and logsInspect public message state, normalized events, and webhook delivery summaries without exposing provider payloads.Workflow failures and debuggingTrace trigger matching, validation, branch decisions, node failures, variables, integrations, and usage.A WhatsApp message was not deliveredSeparate request acceptance from final delivery and check Sender, recipient, template, service window, events, and Balance.