Troubleshooting
Troubleshooting
What the error codes mean
When WarnFire turns an event away, the number it answers with tells you exactly which kind of problem you have:
| Code | In plain terms | Where to look |
|---|---|---|
400 | The message was malformed — a missing required field, a bad timestamp, or a value over its limit. | Compare your request with Send your first event. |
401 | The integration key wasn’t recognized — wrong, expired, or revoked. | Configuration → Services — check the key’s status, or rotate it. |
403 | Your workspace is suspended, usually over billing. | The workspace owner can sign in and settle it under Billing. |
404 | The web address is wrong — often a mistyped adapter name. | Check the URL against the adapter’s docs page. |
409 | A delivery ID was reused to mean something different. | Dedup & retries explains the rule. |
413 | The message was too large. | Trim the payload; link to big data instead of embedding it. |
429 | Too many new problems too fast, or too many incidents open at once. | Limits and protections. |
Every response carries a correlation ID — a short reference number. Note it down; it lets support find your exact request.
“The incident opened, but nobody was paged”
Walk this list top to bottom — it’s ordered by how often each one is the answer:
- Is there a maintenance window active? The incident will say “Paging paused for maintenance.” That’s deliberate quiet time, not a fault.
- Is everything switched on? The responder, schedule, escalation policy, and service each have an enabled/disabled state. The Overview page’s readiness banner flags any broken link in the chain — with a Fix → button.
- Is anyone actually on call right now? A schedule can have gaps. Its card shows On call now — if it says Uncovered, adjust the layer times or add an override.
- Was it a repeat? If the same problem was already open, your event became an update on the existing incident — check its Updates tab. Nobody is re-paged for updates; that’s the deduplication working.
- Can the phone be reached? In the app’s Settings tab, the footer should say Notifications: On. If it says Permission needed, enable notifications for WarnFire in the phone’s settings.
“The notification opened the wrong screen”
Update to the newest app version. If it keeps happening, tell support roughly when it happened, your app version, and the correlation ID shown in the app — never your access code or a push token.
Getting help
Write to WarnFire support with what you expected, what happened, and the correlation ID.
One rule protects you: never send an access code, integration key, or console token to anyone — support will never ask for one.