It looks like we’ve had quite a number (20 or so) failed transactions over the past week. When these transactions fail, they still contribute to the registration numbers and events appear as sold out if they are close to full.
I found the registrations in question and deleted them. They now appear as cancelled and the events can take more registrations.
They appear to possibly be a spam bot as they have no contact details, how best to stop these? Also surely shouldn’t these not count to ticket numbers if they fail?
We can’t be expected to monitor this and delete them everyday.
That wouldn’t necessarily mean a spam bot. If someone added a course to their cart, then stopped there and didn’t fill out the registration form, that would also result in a ticket reservation with no name attached. You shouldn’t need to delete those though.
If you have a sold out event (that shouldn’t be sold out), does it help if you go to Event Espresso > Maintenance > Reset and click on the Reset Ticket and Datetime Reserved Counts button?
I had to delete the failed registrations because they were impacting quite a number of events (small courses in this instance) that are close to closing. Missing out on one enrolment is not approppriate.
It’s quite strange that this appears to be happening only in the last week. There was another one overnight, Australian time.
I’ll answer your question about reducing bots, but you should try to understand that a registration created by a bot or by a person that abandoned the cart will not count as a sale, and thus will not count toward the registration limit. Something else is most likely causing the issue with the premature sold out events.
The support post ‘Failed Transactions (2)’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
Support forum for Event Espresso 3 and Event Espresso 4.