Server-Side
Error Handling & Retry
Queue-based event processing, retry logic, and collect endpoint status codes.
Tugus processes events queue-based via Laravel Horizon. Delivery failures are retried automatically.
Retry logic
| Attempt | Delay | Behavior |
|---|---|---|
| 1 | immediately | First delivery attempt |
| 2 | 60s | Exponential backoff |
| 3 | 300s | Exponential backoff |
| 4 | 900s | Final attempt |
| — | — | Status → failed, health check alert |
HTTP status codes — collect endpoint
| Status | Meaning |
|---|---|
| 202 | Event accepted and queued |
| 400 | Invalid payload (missing event field) |
| 401 | Invalid or unknown API key |
| 422 | Validation error (e.g. value is not a float) |
| 429 | Rate limit exceeded (plan-dependent) |
Checking delivery status
In the dashboard under Live-Stream, the delivery status of every event is visible in real time per platform. Failed deliveries, including the error message from the target API, are shown under Properties → Health.
A 202 from the collect endpoint only means that Tugus accepted the event — not that forwarding succeeded. Check the delivery status separately in the dashboard.