Since the member id is the unix timestamp, running a batch of registrations through results in most of them failing to get into the db. Basically, another registration will get through every second.
Changing the member id to be something different will probably require a little more thought. Easiest workaround right now is to add a second of delay between registrations. A little annoying to wait through a batch, but they will at least be entered.
Since the member id is the unix timestamp, running a batch of registrations through results in most of them failing to get into the db. Basically, another registration will get through every second.
Changing the member id to be something different will probably require a little more thought. Easiest workaround right now is to add a second of delay between registrations. A little annoying to wait through a batch, but they will at least be entered.