PatrickIgnoto That’ll vary site to site. The saved browser state is essentially a snapshot of cookies plus local/session storage, so it inherits whatever session rules the site enforces.
If the site expires sessions after X minutes of inactivity, restoring that state later won’t necessarily override that, the session may already be invalid by the time you reuse it. In some cases it’ll still work if the cookies are long-lived, but for stricter session handling you’ll likely run into the same timeout behavior.
If your wrkflow runs on a recurring basis, a good pattern is to re-save the browser state at the end of each successful run. That way you’re always working off a fresh session and reducing the chances of hitting expired auth.
