Troubleshoot vehicle state
Use this flow when a vehicle is duplicated, missing, stored incorrectly, or has mismatched key or ownership state. Avoid direct production SQL edits before tracing the responsible transition.
Evidence to collect
- Commits for garage, vehicle keys, core, dealership, and persistence resources
- Plate, citizen identifier, garage, state before/after, and relevant logs from a test vehicle
- Local schema/config diffs and resource restart timing
- Whether the error follows purchase, store, retrieve, impound, reconnect, or restart
Safe diagnostic
- Reproduce one transition on staging and query the record before and after it.
- Trace every writer for the vehicle state/garage fields at the pinned commits.
- Normalize plate handling at system boundaries and verify entity existence/ownership server-side.
- Test without local patches to separate upstream behavior from integration conflicts.
Fix
Make one server-authoritative resource own each transition and align its schema/config with the deployed commit. Add logging around failed transitions and test the complete vehicle lifecycle.
Rollback
Restore the previous compatible resource set and database snapshot. For a single test record, use a reviewed, targeted correction only after capturing its prior values.
Sources
Found an issue in this guide?
Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.
Multicharacter loading
Trace QBCore loading failures from startup to character selection, login, housing and spawn. Diagnose new-character failures and a pinned NUI callback defect.
Voice chat
Diagnose QBCore proximity voice, radio and phone calls separately. Check pma-voice settings, saved keybindings, competing resources and channel restrictions.