
ShaunL.32887 (Customer) asked a question.
Social Transaction Expired (400 Bad Request)
Has anyone seen below error with users authenticating using a social provider? Many of our users are reporting it, especially recently. Are there are steps we can take to prevent this?

Hello @ShaunL.32887 (Customer) Thank you for reacting out to our Community!
The problem here might be the routing rules you have setup for IDP's or if there are no routing rules, users are not directed to the correct IDP for login. Please see doc below on how to setup Routing Rules:
https://okta-help.pixtulate.com/en-us/Content/Topics/Security/configure-routing-rules.htm
The Okta Community Catalysts Program is now live. Collect online badges when you participate in the Okta Help Center Questions community. Learn more here.
The October issue of the Okta Community is here and packed with tips on certification, how to earn badges, and new releases. Let us help you stay connected.
Paul,
Thank you for the response. We do have routing rules and majority of Social logins work correctly.
I'm hoping someone with knowledge of the Okta code can let us know the exact set of conditions that lead to this error. It presents like a caching problem.
Hello @ShaunL.32887 (Customer) You might want to do a network trace or SAML trace to see what could cause this issue, there could be a number of things that could case this problem.
https://okta-help.pixtulate.com/oag/en-us/Content/Topics/Access-Gateway/troubleshooting-with-har.htm
https://okta-support.pixtulate.com/help/s/article/Capturing-A-Fiddler-Trace-For-Okta-Customer-Support?language=en_US