Troubleshooting Guide
Common oxide-postaljob problems and fixes — clocking in, loading the van, deliveries and cancelling, the van, crews, pay, settings, missing models, the interface, and phone messages.
Common problems and how to fix them, roughly in the order they tend to come up. Work down each list from the top — the first check is the most likely one.
Most settings mentioned here are changed in-game with /postaljob settings (admins only). Once the resource has started for the first time, editing a config file does nothing until you restart the resource and press Reset to default on that setting — see How Settings Work.
Clocking In
Loading the Van
Deliveries
The Van
Crews
Pay and Progression
Settings
Interface
Turning On Debug Logging
Turn on Debug logging (Config.Debug = true) in the in-game /postaljob settings editor (General, on the Advanced tab). The change saves to your database and applies instantly — no restart needed.
The console will then print [oxide-postaljob] lines for shift state changes, clock-ins/outs, route generation, loading, payments, crew events, vehicle spawn/destruction, and progression changes. Turn it back off when you're done — it's chatty.
When Reporting an Issue
Please include:
- your framework (QBCore, Qbox, or ESX) and which phone/target/key resources you run
- any errors from the server console
- any errors from the client F8 console
- exact steps to reproduce
- whether it happened solo or in a crew