We have started to get intermittent "Invalid OTS Token" errors today when creating a new user profile. Most of our attempts to create a user profile work fine and, prior to today, we recieved an occaisional error every couple of weeks. We have found that if a customer gets this error (nine so far today) and they refresh the checkout page to initiate a new transaction, their next attempt works fine.
Is anyone else seeing an uptick in these errors today? Any good way to mitigate?
Solved! Go to Solution.
04-03-2017 12:30 PM
We believe we found and fixed the issue, and our own monitoring shows a drastic decrease in E00114 errors.
@dbroome -- thank you for confirming you see improvement.
@DoomHamster and @AgileWorkshop -- thank you for your details. Could you please confirm if you see improvement?
04-05-2017 01:49 PM - edited 04-05-2017 01:51 PM
Hello @DoomHamster
Are you still experiencing this issue? If for your production account, I would suggest contacting customer support by phone at 877-447-3938 to report the issue. They are more familiar with production issues and can route your question appropriately. Feel free to ask for escalation.
Richard
04-04-2017 10:29 AM
They are the ones that recommended I post here. :)
Edit: in fact, we have contacted them twice via chat and once via phone and, in each case, they referred us to this forum or the email contact form (which we have also submitted).
To answer your question, yes, we were recieving this error on our production account until we disabled the feature temporarily at 10 AM. We have double checked our configurations but, honestly, that seems like a non-starter since the issue is intermittent and the majority of the requests are successful. We have had our network guys look into the possibility of latency issues but they have seen nothing to indicate a network related issue.
04-04-2017 10:37 AM - edited 04-04-2017 10:51 AM
@DoomHamster Hmm... If you were given a case number, I can ask the team to review.
04-04-2017 10:50 AM
We were never given a case number.
In each case they said that this is clearly an issue better suited to the developers and refered us to you. We were also told that this error should not occur at all unless we are in sandbox mode which we clearly aren't since most of our requests are successful and result in credit cards being saved which we can then see in our live CIM.
04-04-2017 10:59 AM
@DoomHamster Would you mind sending me a private message with your gateway id, that will allow us to investigate further.
Richard
04-04-2017 11:02 AM
Done!
04-04-2017 11:05 AM
We have also started seeing this error. It has happened 127 times in the past 24 hours. Is there a solution for it yet?
04-05-2017 05:56 AM
I'm both sorry to hear that and glad to know we aren't alone at the same time!
04-05-2017 06:17 AM
@DoomHamster, you imply that you saw an uptick in errors starting April 3 -- is that correct?
@dbroome, when did you see these errors start?
04-05-2017 08:07 AM