>I read the message but I'm not in the listing. Is this updated after some specific time?

I need to optimize that logic as the number of requests received in the same second is too high. Thus, it creates a violation of the candidate key even when two different members are inserting at the same time. The problem is when they insert at the same time, the candidate field values is the same (blank), thus, that coincidence happened around 20h03 EDT tonight and I will have to optimize the code to deal with it, additionnaly to the current structure in place, the same way as locking the primary key value in the master table.