Troubleshooting and reference
Diagnose a sending or integration problem, then look up the exact status, event or error code.
catalog · reference · statuses · events list
Start with the symptom
Section titled “Start with the symptom”| What you see | Check first | Continue with |
|---|---|---|
| An email was not sent | Read its status and the recorded reason. Suppressed is different from Queued. |
Sending restrictions |
| An email is delayed | Check domain verification and today’s sending status. | Sending and deliverability |
| A flow has no runs | Check that it is published and its trigger event occurred. | Flow troubleshooting |
| A store is not syncing | Check the store connection and plugin status. | Store connections |
| An API call failed | Read the HTTP status, then errors[].code when a body is available. |
API responses |
| A webhook did not arrive | Check the endpoint, signature validation and retry history. | Webhook guide |
Look up an identifier
Section titled “Look up an identifier”Search the exact code or status you see. These catalogs are generated from Azimea’s code; the status explanations include the next action to take.
- Why an email was not sent
- Consent statuses
- Carts and orders
- Email statuses
- Flow runs
- Events
- Error codes
Ask for help
Section titled “Ask for help”If the checks do not resolve the issue, contact support. Include the page where it happened, the error code, the time and the relevant message or run ID. Do not include API keys or webhook signing secrets.