Troubleshooting
Troubleshooting hub
Start with the symptom, preserve identifiers, and narrow failures across workflows, schedules, WhatsApp, integrations, billing, and developer services.
EveryoneBeginnerAvailable
What this guide covers
- The hub routes each visible symptom to the evidence and service most likely to explain it.
- Prerequisites: Record the Agent Project, approximate UTC time, feature, and safe public identifier before retrying.
- Result: You identify the first failing boundary and correct it without duplicating side effects.
- Limit: Support diagnostics must not include API keys, authorization headers, provider tokens, webhook secrets, full recipient lists, or unnecessary message bodies.
What this is and when to use it
The hub routes each visible symptom to the evidence and service most likely to explain it.
| Use it when | Expected outcome |
|---|---|
A Yanola action did not produce the expected result. | You identify the first failing boundary and correct it without duplicating side effects. |
Before you begin
- Record the Agent Project, approximate UTC time, feature, and safe public identifier before retrying.
Prerequisites
Record the Agent Project, approximate UTC time, feature, and safe public identifier before retrying.
Complete the task
- Identify whether no operation started, an operation failed, or it completed with unexpected output.
- Check status, saved configuration, connections, number, template, entitlement, and Balance.
- Use the service-specific page below.
- Avoid repeated retries when acceptance or billing state is uncertain.
Confirm it worked
- You identify the first failing boundary and correct it without duplicating side effects.
Common problems
| Symptom | What to check |
|---|---|
No identifier exists | Start with workflow/schedule status and trigger matching. |
A request was accepted but no delivery arrived | Inspect asynchronous message events rather than sending a duplicate immediately. |
Current limitations
Support diagnostics must not include API keys, authorization headers, provider tokens, webhook secrets, full recipient lists, or unnecessary message bodies.
Product boundary
Support diagnostics must not include API keys, authorization headers, provider tokens, webhook secrets, full recipient lists, or unnecessary message bodies.
Where to go next
Related documentation
A workflow is not runningCheck Active status, saved validation, trigger matching, selected number, schedule timezone, and webhook input.A WhatsApp message was not deliveredSeparate request acceptance from final delivery and check Sender, recipient, template, service window, events, and Balance.Errors and retriesHandle Yanola error envelopes consistently and retry only transient or rate-limited failures.