Hello @Carolina SILVA ,
Thanks for reaching out and again for the follow-up confirmation that during the subsequent attempts you were able to create the support request, and are currently in a good state for creating the request however you are still following up with the other odd behavior, I'll check in on the support requests to see what the status is.
But for this issue, I looked over your account and checked some details on the backend and I was not able to identify any absolutes on what happened. So for what caused the issue in the first place, I can only speculate at this point without being able to reproduce the behavior or collect additional information while the error is occurring, but the primary suspicion would be an expired session token from corrupted browser caching, as it’s necessary to be logged in to raise the request if the browser caching was experiencing an issue corrupting a session token in transit or a session token was expired this type of behavior could be the result.
Refreshing the browser or closing out and re-opening the browser would refresh the tokens and as it started working on a follow-up action this is my primary suspect, but again cannot verify, unfortunately.
But in the future, if you run into something like this and you are a verified licensed support contact the option to create a support request without the Customer Advocates team is always available to any user by submitting billing and licensing issues in the contact form vs a technical issue request, and the Customer Advocates team would be able to either clear up any login issues or would be able to route your request to the support team after verifying your account so we could dig into the issue further and help isolate the issue.
I know this is not a solid answer but hope it helps out.
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.