Troubleshooting

Fixes for common problems.

Mayo Notify doesn't start

Check the console for errors from mayo_notify. A start-up error about escrow? See Escrow errors.
Don't rename the mayo_notify folder.

The patch or provide line isn't in place yet. See Replacing your notify.

ox_lib, QBCore or ESX: check the line is the first line inside the function, and restart the framework or ox_lib after editing it.
okokNotify, mythic_notify, pNotify, t-notify or esx_notify: the old resource has to be stopped and removed, and its provide line uncommented in mayo_notify/fxmanifest.lua. Restart the server, not just the resource.

The old notify resource is still running. Remove its ensure from server.cfg and restart the server.

On Qbox and QBCore, alerts only reach players on duty. Go on duty, or set Config.Alerts.OnDutyOnly = false.
Check the job name matches the framework's job name exactly, like police, not Police.
Start Mayo Notify after your framework in server.cfg. It checks for the framework when it starts.
On standalone servers, give the job's group its ACE. See Permissions.

The key only works while the alert is on screen, and only for the latest alert.
The alert needs coords.
The key may be bound to something else. Players can change it in Settings > Key Bindings > FiveM, under Set waypoint to the latest alert.

Add add_ace group.admin mayo_notify.announce allow to server.cfg and make sure you're in group.admin. See Permissions.

Font Awesome icons and the font load from the internet. If players are behind a firewall that blocks them, use the built-in icons instead: see Types.

Check Config.Sounds is true, and that the type has a sound in Types.