FAQ & Troubleshooting
"My command says I'm not linked"
Run /kestrellink <code> with a fresh code from the web app's Account
Settings → Link FiveM Account. Make sure the character you're playing
when you run it is the one you meant to link — Kestrel tracks status per
active character, not per account, so linking while your civilian
character is active won't help your cop character.
"It says I need to be on duty"
Toggle duty with /kestrelduty (ESX/standalone) or your framework's own
duty command (QBCore's /duty). Almost every staff command — lookups,
citations, arrests, BOLOs, the MDT — requires linked and on duty.
"The radio HUD just shows a percentage, I can't hear anyone on it"
That readout is a signal-quality simulation, not voice audio — it doesn't touch what you hear at all. Actual two-way voice radio is a separate feature; ask your admin whether your server runs it. See Radio & Communications for the full picture of both features and how they differ.
"I don't get a GPS waypoint when dispatch assigns me a call"
This needs your organisation's map configured for real in-game
coordinates (gta_v_tiles), not a static image — that's an admin setting
under Settings → Map. Ask your community's admin to check it.
"I ran /bolocheck / got a hit notification but can't see the full details"
Some BOLO information is restricted by department. Fire/EMS units see enough to stay safe on scene (description, location, severity) but not the issuing department's investigative narrative or internal notes — this is intentional, not a bug.
"I claimed my civilian record but it's not the one I expected"
/kestrelclaim links your currently active character's auto-created
civilian record. If you play multiple characters, make sure the one
you're trying to claim is the one currently loaded.
"ERS created a call I didn't expect"
If your server runs kestrel-ers-bridge, accepting a callout or turning
your siren on during a stop creates a call automatically — that's by
design, not a glitch. If a stop-related call seems to be lingering after
you've clearly wrapped it up, flag it to a dispatcher rather than assuming
it'll self-resolve; not every path through a stop automatically closes the
call.
"I ended my traffic stop but it's not clear what happened to it"
Ending a stop always requires picking an outcome (Warning, Citation, Arrest, No Action, or Other) — if you back out of the MDT instead of picking one, the call stays open and attached to your unit. Reopen the Traffic Stop tab and finish ending it properly, or ask a dispatcher to close it from their side. See Officer Field Guide for the full flow.
"My field contact turned into a case, but I can't find the original stop from the report"
That's expected — a field contact and the RMS report it leads to aren't linked automatically. If you want the connection preserved, mention the original stop in the report's own narrative. See RMS & Incident Reports.
"I can't submit my own report for approval and have someone else review it in one step"
Self-review is blocked on purpose — the person who approves or returns a report always has to be someone other than its author, even if you hold a permission that would otherwise let you approve reports. Have a different supervisor review it.
Something else looks wrong
If a lookup, citation, or BOLO command silently fails with no chat response at all, that's usually a server-side configuration issue (a missing or misconfigured integration credential, or a department mapping problem) rather than something you can fix from your end — report it to your community's admin rather than retrying repeatedly.