Troubleshoot inventory updates
Use this flow when resources report missing inventory functions, items disappear, or inventory UI fails after an update. Never create guessed tables or columns from an unrelated guide.
Evidence to collect
- Deployed commits for
qb-core,qb-inventory, and each failing caller - The first server/client error with resource and line number
- Local diffs, relevant manifest order, and the exact upstream SQL at the deployed commit
- One affected test character and item, without exposing personal identifiers
Safe diagnostic
- Reproduce on staging with a database copy whose sensitive data has been minimized.
- Trace the failing call to current upstream exports/functions instead of renaming blindly.
- Compare shared item definitions and inventory schema with the same commit.
- Check that
qb-coreandqb-inventorystart before dependent resources.
Fix
Update callers to the API that exists at the pinned commit, then apply only reviewed upstream schema changes through your migration process. Smoke-test add, remove, use, transfer, stash, and reconnect.
Rollback
Restore the previous resource commits and database snapshot as one compatible unit. Do not retain a new schema with old code unless that combination was explicitly tested.
Sources
Last updated on