Support
Get Queuebeam working reliably.
For account or delivery incidents, email support@queuebeam.cloud and include the operation ID. Never send API keys or provider secrets.
First dispatch
- Create and verify your tenant.
- Create an API key and store it in your Laravel app.
- Configure a destination or BYO email provider.
- Send an operation and inspect its timeline.
Common errors
- 401 Unauthorized
- The API key is missing, revoked, copied incorrectly or belongs to another environment.
- 422 Unknown destination
- The named Slack, webhook or callback destination is not configured for the tenant.
- dead_letter
- All attempts were exhausted. Open the operation, inspect attempts, fix the destination and replay it.
- Email rejected
- Check provider credentials, verified sender identity, SPF, DKIM and DMARC alignment.
What to send support
Operation ID, approximate UTC time, operation type, expected outcome and whether replay is safe. Queuebeam support can inspect encrypted tenant data only through audited administrative access.
Service checks
Use tenant healthchecks for uptime monitoring. They return HTTP 503 when your configured queued or failed thresholds are reached.