A session-expired message means BEHCA no longer has a valid browser session or mobile sign-in token.
Browser sessions
Organizations can set a browser inactivity timeout from 30 minutes to 24 hours. The default is 90 minutes. BEHCA shows a warning and gives you 15 minutes to stay signed in before logging out.
You may also lose a browser session if:
- The BEHCA cookie was deleted or blocked
- You closed a private or incognito window
- Browser privacy settings or an extension removed the cookie
Changing MFA settings does not by itself reset active BEHCA sessions. A server restart, device clock, or signing in on another device is not a documented cause of a BEHCA session expiring.
Mobile sessions
The mobile app sign-in token is valid for seven days. Web and mobile sessions are separate, so being signed in on the web does not sign in the mobile app.
What to do
Sign in again. If you have unsaved work in a browser tab:
- Leave the original tab open.
- Open BEHCA in another tab and sign in.
- Return to the original tab and try saving.
This may recover the save, but it cannot guarantee that unsaved data will remain available.
"I keep getting logged out" on the web
Check the organization's timeout
Ask a Manager or Billing user what browser inactivity timeout the organization uses.
Allow BEHCA cookies
BEHCA needs cookies for app.behca.com (US) or au.behca.com (Australia). Do not block all cookies for the site.
Avoid private browsing
Private windows discard their cookies when the window closes.
Check privacy extensions
If a privacy or security extension clears site data, allow BEHCA or test in another browser.
Sign-in loop
If signing in immediately returns you to the login page:
- Clear BEHCA site data and cookies.
- Close and reopen the browser.
- Try signing in again.
- Try another supported browser.
Mobile app keeps asking you to sign in
- Update BEHCA to the latest version
- Force-close and reopen the app
- Sign in again
- If the problem continues, reinstall the app
When to escalate
If a fresh sign-in expires again within a few minutes, contact Support with the device, browser or app version, exact message, and the time it occurred.