high
confirmed
oxmysql / database · AGN-KB-DB-0002
oxmysql: duplicate entry (ER_DUP_ENTRY)
The message
ER_DUP_ENTRY
The server refused to store the same thing twice. Usually that is protection working, not damage.
What you see
- An action fails the second time it is performed
- A purchase, registration or creation step errors out
What usually causes it
- A unique key doing its job: the row already exists
- A double-submit or double-fired event creating the same row twice
- An id generator producing a collision
Worth checking first
- Identify the key named in the error
- Check whether the action can be triggered twice quickly
- Check whether a previous attempt partially succeeded
Safe steps, one at a time
- Player-side: do not repeat the action; report what you were doing
- Staff: decide whether the duplicate is a bug or the constraint correctly preventing one, and handle it explicitly rather than removing the key
These are suggestions, not instructions. Do only what you are comfortable with, back up anything important first, and stop if a step does not match what is on your screen. Advice, risk and responsibility.
When to stop and ask staff
Staff. Escalate faster if it involves a purchase or an item.
Looks like
AGN resource / QBCore
What staff will need
- Exact error with key name
- The action performed
- Whether it was repeated
Last reviewed Fri Sep 18.