Skip to content
HeartBeatAgents

Signing In Fails

View as Markdown

What a specific sign-in or single sign-on error actually means, whether it's your password, your account, or your identity provider.

Password sign-in

"Invalid email or password": exactly what it says; this is deliberately vague between a wrong email and a wrong password, so it can't be used to check whether an email has an account.

"Too many attempts": sign-in is rate-limited after repeated failures. Wait a moment before trying again rather than retrying immediately.

"This instance has reached its maximum number of accounts": your plan's account limit is reached; a platform administrator needs to upgrade before another account can be created.

Single sign-on

"Single sign-on is not enabled for this instance": your organization hasn't turned SSO on, or you followed an old link from before it was configured. Use password sign-in, or ask your administrator.

"Your email domain is not permitted to sign in via SSO": SSO on this instance is restricted to specific email domains, and yours isn't one of them. This is a configuration decision by your administrator, not an error to retry.

"No account exists for this address": your organization's SSO is set to require admin provisioning, meaning an administrator has to add your account first before you can sign in through SSO at all, even with a valid identity-provider login.

"This account has been disabled": an administrator disabled this specific account. Contact them; there's nothing to fix on your end.

"Your sign-in request expired": the SSO flow itself timed out, most often from taking too long on your identity provider's own login page. Start over.

"Single sign-on failed" or "could not be completed": a generic failure from the identity-provider exchange itself. Try again; if it persists, an administrator should check the issuer URL, client ID, and client secret under Settings → SSO, since a misconfigured value here produces exactly this symptom.

Password recovery when SSO is enabled

If your organization has SSO on, password recovery is intentionally unavailable: it's managed by your identity provider instead. Sign in through SSO, or contact your administrator.