> For the complete documentation index, see [llms.txt](https://mango-5m.gitbook.io/mango5m-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mango-5m.gitbook.io/mango5m-docs/resources/mango-dispatch/reference/troubleshooting.md).

# Troubleshooting

The handful of things that actually go wrong, and how to fix each one.

<details>

<summary>Nobody receives alerts</summary>

Check, in this order:

1. **Are they a unit?** Press `F7`. If the window does not open, they are not. Job names in `Config.Recipients.jobs` must be the framework's **names**, not labels - `police`, not `Police Department`.
2. **Is a framework detected?** Run `mango_dispatch_bridges` in the server console. If Framework reports `none`, jobs cannot be read at all - see [Framework and Bridges](/mango5m-docs/resources/mango-dispatch/configuration/framework-and-bridges.md).
3. **Is `requireOnDuty` on** while nothing on your server sets a duty flag? Set it to `false`.
4. **Was the call silent?** `silent = true` creates the call without alerting anyone. It will still be in the window.

</details>

<details>

<summary>The window opens but is always empty</summary>

The window only lists **open** calls. A call that was cleared or auto-resolved is gone from it - by design.

If calls are being raised but never appear, check the server console for the create: with `Config.Debug = true` you get a `call #N created` line per call. No line means `CreateCall` rejected it, and the usual cause is **invalid or missing coordinates** on a server-side call, which makes it return `nil`.

</details>

<details>

<summary>Alerts stopped after someone changed job</summary>

Unit state is re-checked every 30 seconds, so give it half a minute. If it never updates, the framework bridge is probably returning a stale job - jobs are cached for 5 seconds inside the resource, so a longer delay is coming from your framework rather than from here.

</details>

<details>

<summary>Keys do nothing</summary>

Non-units are ignored by every key, so confirm unit status first. Then check FiveM's **Settings > Key Bindings > FiveM** - once FiveM has stored a binding for a player, changing the default in `config/config.lua` does not move their key. A key set to `''` in config is intentionally unbound and has to be mapped there by the player.

Also remember the context rules: Code 4 and Take Primary do nothing unless you are on a call, and accept does nothing when you are already responding.

</details>

<details>

<summary>No alert sound</summary>

1. `alertSound.enabled` must be `true`, and `file` must name a file that exists in `web/sounds/`.
2. A new file needs a `refresh` and a `restart mango_dispatch` before it is served.
3. Per-call `sound` values are sanitised - anything that is not a letter, digit, dash, dot or underscore is stripped, so `../custom/alert.mp3` will not resolve.
4. A missing file fails silently by design, so check the name carefully.

</details>

<details>

<summary>All the calls vanished</summary>

Expected after a restart. Calls are held in memory and every open call is closed when the resource stops - see [Performance](/mango5m-docs/resources/mango-dispatch/reference/performance.md) for why, and [Events](/mango5m-docs/resources/mango-dispatch/developer-guide/events.md) if you want to log them permanently yourself.

</details>

<details>

<summary>A blip or route is stuck on someone's map</summary>

Responding blips are removed when you cancel, clear the call, or the resource stops. If one survives, something else on your server is drawing it - this resource creates exactly one blip per responding player and removes it on `onResourceStop`.

</details>

<details>

<summary>The HUD editor will not close, or the layout will not save</summary>

`Done` saves, `Reset` clears back to defaults, `Esc` closes without saving. The layout lives in the player's local storage under `mango_dispatch_hud_layout`, so it is per player and per machine - clearing FiveM's cache resets it.

</details>

<details>

<summary>Notifications appear twice, or not at all</summary>

Run `mango_dispatch_bridges`. If Notify resolved to something you did not expect, pin it explicitly in `config/bridge.lua` - `Notifications = 'mango_notify'`, `'ox_lib'`, `'builtin'` or `'custom'`. Doubles usually mean a custom provider is triggering an event that your notify resource already draws.

</details>

### Getting more detail

```lua
Config.Debug = true
```

Prints `[mango_dispatch:DEBUG]` lines when calls are created and when units register, with the registering resource's name. Turn it off on a live server.

### Still stuck?

Head to [I Need Support](/mango5m-docs/i-need-support.md) with your `mango_dispatch_bridges` output, your `Config.Recipients` block, and whether the call shows up in the window at all.