After further investigation into this, it appears that the majority of users maintained or had their SDK user session restarted since the incident on 7/11. Clients using the Legacy SDK (1.x.x) are encouraged to direct any users that may be affected to the workflow within their application that checks for a current SDK session and starts the SDK user session if one isn't present. It is best practice to do that on app launch or login to the client's application.
Posted Aug 08, 2025 - 10:14 EDT
Identified
We are currently investigating an issue identified from our network event on July 11, affecting user sessions within the Validic Legacy SDK (v1.x.x). Some user sessions may have ended unexpectedly due to authentication errors occurring during network downtime.
Clients using the Legacy SDK should verify that a Validic SDK user session is active during app launch or user login, and restart the session if it's not present.
Our investigation into the exact scope of impact and recovery options continues. Additional updates will follow as we confirm more details.