Skip to main content

Troubleshoot MFA and Sign-in Problems

Most MFA problems come from a wrong phone clock, an old code, or the wrong entry in the app. Find your symptom below.

Common problems​

What you seeLikely causeWhat to do
The code didn't match when turning MFA onThe phone's clock is wrong, or an old code was usedSet the phone's date and time to automatic, then enter the newest code
Code rejected at sign-inWrong account in the app, or clock driftPick the Biznsbook entry in the app and set the phone clock to automatic
Account temporarily lockedToo many wrong passwords or codesWait about 15 minutes, then try again
Every page sends you to Multi-factor authenticationYour role requires MFAFinish setup. You can then use the app normally
Backup code rejectedIt was already used, or a newer set replaced itUse another code from your newest set, or ask your administrator to reset MFA
No recovery emailAddress wrong or message blockedCheck spam, then ask your administrator to reset MFA
Can't turn MFA offYour role requires MFAAsk your administrator if it should be removed

Common questions​

  • Can I get codes by SMS or email? No. Codes come from an authenticator app, which is safer than SMS and works offline.
  • Do I need a code on every device? You need one at each sign-in, unless you ticked Remember this device on that browser (30 days).
  • Which apps work? Any time-based authenticator app, including Google Authenticator, Microsoft Authenticator, Authy, 1Password and Bitwarden.

:::info Administrators can see what happened MFA sign-ins, failures, lockouts and setting changes are recorded in the security audit log. :::

Next step​