Documentation
The Console Freezes And Prints A Rename ErrorCause: the resource folder was renamed. The resource checks its own name on startup.Solution: the folder must be na
Cause: the resource folder was renamed. The resource checks its own name on startup.
Solution: the folder must be named qs-job-management. Rename it back and restart.
Cause: the admin check failed.
Solution: the admin panel is granted only by the ESX group admin / superadmin, or the QBCore permission admin. Nothing else grants it — job grades and canOpenMenu do not.
Remember: /boss is the admin panel. The boss menu is opened at the job's boss location with [E].
Cause: one of three checks is failing.
Solution: all of the following must be true:
The job has an entry in Config.BossLocations, or a location added from the panel's Location tab.
The job is the player's active job — not just one they hold.
The player is the boss, or holds a grade with canOpenMenu.
Cause: the job is hidden, or the player was pushed back to unemployed.
Solution: check whether the job is listed in Config.BlackListedJobs (it is still stored, just not shown), and whether the player is over Config.MaxJobs — or over Config.NoLicenseUserMaxJobs if Config.UseByLicense is enabled.
Cause: the player is off duty.
Solution: this is expected behaviour. Toggling duty sets the framework job to unemployed grade 0, and toggling it back restores the job and grade. Any script reading the player's job while they are off duty will see unemployed.
Cause: the job resource is not started, so its table cannot be read.
Solution: the resource named in Config.JobStatsTables must be running. Level and XP are read from that resource's own table, not from Job Management.
Cause: the job resource is still paying players directly.
Solution: route the payment through the export instead:
exports['qs-job-management']:AddJobMoney(src, amount, 'miner')This is also what feeds the stats, so direct payments leave both the treasury and the earnings history empty.
Cause: one of the four salary conditions is not met.
Solution: check all four:
The rank has an amount above zero.
The interval has elapsed.
The employee is online.
With fromTreasury enabled, the balance covers the payment — otherwise it is skipped entirely.
Cause: on ESX the job is written to the jobs and job_grades tables, but on QBCore/QBox it is only added to the shared jobs table in memory.
Solution: add the job to qb-core/shared/jobs.lua to make it persist.
Cause: the /badge style commands read a Config.Commands table that no longer exists in the config, so they never register.
Solution: give and remove badges from the boss menu instead.
Cause: the data/*.json files ship with data from the development server.
Solution: empty them before going live — see the installation guide. This affects treasury balances, reports, stats and logs.
Cause: the resource keeps these files in memory and writes them back.
Solution: edit them only while the server is stopped.
Cause: your locale file is incomplete or outdated after an update.
Solution: missing keys fall back to English automatically, so this is a warning, not a failure. Copy the missing key from the English locale into your language file.
Cause: the notification hook is still using the default.
Solution: point it at your own system in config/config.lua:
function SendTextMessage(msg, type)
exports["Notify"]:Alert(msg, type)
end