The resource folder is not named qs-dispatch — for example qs-dispatch-main or qs-dispatch (1). The server shuts down a few seconds later. Rename the folder to exactly qs-dispatch and update the ensure line.

The SQL was not imported, or was imported into another database. Import sql/all.sql into the same database your mysql_connection_string points to, then restart. An error near Loaded … Camera objects or [AUTOCFG] at start-up has the same cause.

Config.Framework is not esx or qb. Restore the auto-detection, or set one of those two values by hand. Make sure your framework is ensured before qs-dispatch in server.cfg.

The script looks up your users table to match its collation and could not find it: the detected framework is wrong. On ESX it reads users, on QBCore players. Check that the right framework starts before qs-dispatch, or pin Config.Framework.

A config value matches no bridge file, usually because of a typo or an unsupported name:

• CreateBill / getBills → Config.Billing.

• SetRadioChannel → Config.voice (pma-voice or saltychat).

• GetPlayerHouses → Config.Housing.

• getCars / getVehsByPlate → Config.VehicleGarages.

Use one of the values listed in Integrations.

The update check could not be reached. It is harmless: the script runs normally. It usually means the server has no outbound internet access or GitHub is unreachable at that moment.

Two conditions are checked continuously, and failing either closes every panel:

• The player's job is in Config.JobsAllowed — with the exact job name, not its label.

• The player is on duty. Type /onduty; on QBCore, also check the framework's own duty state.

Check, in order:

1. The receiver's job is in the call's job field and in Config.JobsAllowed, and they are on duty.

2. callLocation is a vector3. A plain table { x = …, y = …, z = … } is ignored by the receiving client.

3. The event name is exactly qs-dispatch:server:CreateDispatchCall, triggered with TriggerServerEvent from a client or TriggerEvent from the server.

The call's blip table is missing sprite, scale, colour, text or time, or time is not a number. Note the British spelling: colour, not color.

A script sent otherData as a single entry or a string. It must be a list, even with one line: otherData = { { text = 'Armed', icon = 'fas fa-gun' } }. The call is still sent without the extra lines.

Photos need Config.AllowImages = true and a working Discord webhook in Config.DiscordWebHook. The F8 console prints "Webhook not configured" when it is empty. If the webhook was deleted in Discord, create a new one and paste it.

The call-log webhooks in server/custom/events/onCallEvent.lua are empty. Paste a URL into PoliceWebhookURL and AmbulanceWebhookURL, or delete the warning lines if you do not want Discord logs. It does not affect the dispatch.

• Config.Dispatch.EnabledRadios must be true and Config.voice must match your voice resource.

• The job needs its own entry in Config.Dispatch. Without one, the console prints OnDispatcherUpdate listname is nil.

• The unit may have turned their radio icon off in the panel, which stops automatic moves for them.

Their job needs an entry in Config.JobsBlips with show = true, and the viewer's job must list it in showJobs to see another department. On large servers, OneSync Infinity is needed for far-away units.

• With Config.NeedItemForMDT = true, only the item opens the MDT.

• The job needs an entry in Config.MDT.JobsAllowedToMDT, and the player's grade must be in its gradesAllowedToEdit — by number or by grade name.

• The player must be on duty.

The item must exist in your inventory with the same name as Config.MDTItemName and be marked usable. See Installation for each inventory.

The job of the player using the MDT has no entry in Config.MDT.JobsAllowedToMDT — typically a job opened the MDT through the item. Add an entry for that job.

Config.Billing must match the billing script you actually run. With jim-payments the console warns that it is not fully compatible — set Config.showBillsInMDT = false. Without a billing script, set it to false as well.

Vehicles are read from Config.vehiclesTable; if your garage script stores them in another table, change it. Houses need qs-housing or qb-houses started before qs-dispatch. Also check that CanViewVehicles and CanViewHouses are enabled for that job.

Two charges share the same id in config/jobsdata.lua, and only the first is kept — the F8 console warns about it. Give every charge a unique id. Also check the book lists the player's job in jobs.

Only suspects with charges assigned from the MDT, and within 5 metres, are sent. Charges with a jail time of 0 — such as the EMS services list — never jail anyone. The officer's job must be in Config.Penitencial.JobsAllowedToSendToJail to see the marker at all.

Config.InventorySystem is none. Set it to your inventory. Item names in IlegalItems must match your inventory's names exactly.

The player lacks one of the two aces. The server console prints a suggested add_ace line; add both command.createcameras and dispatch.createCameras as shown in Installation, then restart the server.

Your anticheat sees the camera as a freecam. With Fiveguard, set Config.FiveguardName to its exact folder name so the bypass is granted. The console prints Failed to set permissions when the name is wrong. Other anticheats need a freecam exception for qs-dispatch.

Either the viewer's job is not in Config.DispatchBodyCamZones.jobsAllowed, or needIsInZone is on and they are outside every bodycam zone.

The driver must enter the zone faster than the first limitFrom of its velocityRanges — in km/h, or MPH with useMph. Their job must not be in ignoredjobs, and autoBill must be on. Fines go through Config.Billing unless sendDirectTheBill is off.

That is often by design: with no pedestrians around and no camera nearby, nobody calls. To test, set Config.DebugChance = true. Also check that the shooter's job is not in Config.PoliceJobs, that the weapon is not silenced or blacklisted, and that you are not inside a ZonesWithNoCall sphere.

The DLC did not see the player die. It listens to esx:onPlayerDeath on ESX and hospital:client:SetDeathStatus on QBCore. With another death script, trigger one of those or edit client/death.lua.

The resource folder is not named qs-dispatch — for example qs-dispatch-main or qs-dispatch (1). The server shuts down a few seconds later. Rename the folder to exactly qs-dispatch and update the ensure line.

The SQL was not imported, or was imported into another database. Import sql/all.sql into the same database your mysql_connection_string points to, then restart. An error near Loaded … Camera objects or [AUTOCFG] at start-up has the same cause.

Config.Framework is not esx or qb. Restore the auto-detection, or set one of those two values by hand. Make sure your framework is ensured before qs-dispatch in server.cfg.

The script looks up your users table to match its collation and could not find it: the detected framework is wrong. On ESX it reads users, on QBCore players. Check that the right framework starts before qs-dispatch, or pin Config.Framework.

A config value matches no bridge file, usually because of a typo or an unsupported name:

• CreateBill / getBills → Config.Billing.

• SetRadioChannel → Config.voice (pma-voice or saltychat).

• GetPlayerHouses → Config.Housing.

• getCars / getVehsByPlate → Config.VehicleGarages.

Use one of the values listed in Integrations.

The update check could not be reached. It is harmless: the script runs normally. It usually means the server has no outbound internet access or GitHub is unreachable at that moment.

Two conditions are checked continuously, and failing either closes every panel:

• The player's job is in Config.JobsAllowed — with the exact job name, not its label.

• The player is on duty. Type /onduty; on QBCore, also check the framework's own duty state.

Check, in order:

1. The receiver's job is in the call's job field and in Config.JobsAllowed, and they are on duty.

2. callLocation is a vector3. A plain table { x = …, y = …, z = … } is ignored by the receiving client.

3. The event name is exactly qs-dispatch:server:CreateDispatchCall, triggered with TriggerServerEvent from a client or TriggerEvent from the server.

The call's blip table is missing sprite, scale, colour, text or time, or time is not a number. Note the British spelling: colour, not color.

A script sent otherData as a single entry or a string. It must be a list, even with one line: otherData = { { text = 'Armed', icon = 'fas fa-gun' } }. The call is still sent without the extra lines.

Photos need Config.AllowImages = true and a working Discord webhook in Config.DiscordWebHook. The F8 console prints "Webhook not configured" when it is empty. If the webhook was deleted in Discord, create a new one and paste it.

The call-log webhooks in server/custom/events/onCallEvent.lua are empty. Paste a URL into PoliceWebhookURL and AmbulanceWebhookURL, or delete the warning lines if you do not want Discord logs. It does not affect the dispatch.

• Config.Dispatch.EnabledRadios must be true and Config.voice must match your voice resource.

• The job needs its own entry in Config.Dispatch. Without one, the console prints OnDispatcherUpdate listname is nil.

• The unit may have turned their radio icon off in the panel, which stops automatic moves for them.

Their job needs an entry in Config.JobsBlips with show = true, and the viewer's job must list it in showJobs to see another department. On large servers, OneSync Infinity is needed for far-away units.

• With Config.NeedItemForMDT = true, only the item opens the MDT.

• The job needs an entry in Config.MDT.JobsAllowedToMDT, and the player's grade must be in its gradesAllowedToEdit — by number or by grade name.

• The player must be on duty.

The item must exist in your inventory with the same name as Config.MDTItemName and be marked usable. See Installation for each inventory.

The job of the player using the MDT has no entry in Config.MDT.JobsAllowedToMDT — typically a job opened the MDT through the item. Add an entry for that job.

Config.Billing must match the billing script you actually run. With jim-payments the console warns that it is not fully compatible — set Config.showBillsInMDT = false. Without a billing script, set it to false as well.

Vehicles are read from Config.vehiclesTable; if your garage script stores them in another table, change it. Houses need qs-housing or qb-houses started before qs-dispatch. Also check that CanViewVehicles and CanViewHouses are enabled for that job.

Two charges share the same id in config/jobsdata.lua, and only the first is kept — the F8 console warns about it. Give every charge a unique id. Also check the book lists the player's job in jobs.

Only suspects with charges assigned from the MDT, and within 5 metres, are sent. Charges with a jail time of 0 — such as the EMS services list — never jail anyone. The officer's job must be in Config.Penitencial.JobsAllowedToSendToJail to see the marker at all.

Config.InventorySystem is none. Set it to your inventory. Item names in IlegalItems must match your inventory's names exactly.

The player lacks one of the two aces. The server console prints a suggested add_ace line; add both command.createcameras and dispatch.createCameras as shown in Installation, then restart the server.

Your anticheat sees the camera as a freecam. With Fiveguard, set Config.FiveguardName to its exact folder name so the bypass is granted. The console prints Failed to set permissions when the name is wrong. Other anticheats need a freecam exception for qs-dispatch.

Either the viewer's job is not in Config.DispatchBodyCamZones.jobsAllowed, or needIsInZone is on and they are outside every bodycam zone.

The driver must enter the zone faster than the first limitFrom of its velocityRanges — in km/h, or MPH with useMph. Their job must not be in ignoredjobs, and autoBill must be on. Fines go through Config.Billing unless sendDirectTheBill is off.

That is often by design: with no pedestrians around and no camera nearby, nobody calls. To test, set Config.DebugChance = true. Also check that the shooter's job is not in Config.PoliceJobs, that the weapon is not silenced or blacklisted, and that you are not inside a ZonesWithNoCall sphere.

The DLC did not see the player die. It listens to esx:onPlayerDeath on ESX and hospital:client:SetDeathStatus on QBCore. With another death script, trigger one of those or edit client/death.lua.