Troubleshooting
Common problems and how to fix them in oxide-dispatch.
Common problems and how to fix them. Before deep-diving, know where the logs are: oxide-dispatch sends its logs through the free oxide-logger resource — when it is installed and started, dispatch log lines appear in your live server console and in a daily file at oxide-logger/logs/oxide-dispatch-YYYY-MM-DD.log. Type oxlog level oxide-dispatch debug in the server console to see extra detail while debugging. Without oxide-logger installed, these log lines go nowhere — install and start it first if you need to see them.
Alerts & Broadcast
Detection & Panic
UI & Radial
Status & Callsign
Rate Limits & Expiry
Database & Integration
AI Dispatch issues
The AI Radio Dispatcher feature has its own dedicated troubleshooting section. See the AI Radio Dispatcher guide for:
AI Dispatch unavailable (missing_api_key)on join- Chained mode:
stt_empty/ silent audio - Chained mode: alert created but no voice reply (TTS failed)
- Chained mode: latency feels longer than ~2s
- Realtime mode: token mint fails with status 400 / empty body
- AI says "I can't find anything" when records DO exist (officer not on duty)
- AI doesn't respond at all to PTT
- High OpenAI bills
Getting Help
If none of the above resolves your issue:
Raise the log level (oxlog level oxide-dispatch debug in the server console, requires the free oxide-logger resource) so shim rejections and the full alert lifecycle are visible.
Reproduce the problem and capture the full server console output around the failing operation.
Capture the F8 client console output for popup-related issues.
Note your framework (qb-core / qbx_core / es_extended) and version.
Contact Oxide Studios support with all of the above.