Skip to main content

Resolve email, provider and database errors

Verification and password-reset email​

Check these in order:

  1. Confirm the exact recipient address used in the request or registration form. [email protected] and other example.test sample addresses cannot receive real mail.
  2. Check that mailbox's spam/junk folder as well as the inbox.
  3. Check the selected workspace and the client ID used for the request. The user and template must belong to the intended workspace.
  4. Open Email templates and check the matching saved template: email_verification with {{ verification_code }}, or reset_password with {{ reset_code }}. See template setup.
  5. Request a fresh message through the hosted screen or the resend/reset requests, then use the code from that message in the matching step before expiry.

The expected result is an email containing a real code, followed by successful verification or reset when you submit that code. Creating a template alone sends no message. Verification, password reset and passwordless sign-in use different code purposes.

A generic success message does not confirm account existence or successful delivery. If messages still do not arrive, report the workspace, request time, template name and sanitized response to support. Do not share the code or password.

Social sign-in​

Check provider type, provider-issued client ID/secret, enabled provider status and the provider-to-SyAuth callback URL. Verify that your own application callback is also registered on the SyAuth client. Keep state and PKCE parameters intact through redirects. See provider configuration.

External user database​

Use the connection test and operation logs. Check database reachability, credentials, permissions, schema mapping and the selected action script. An active but unhealthy connection can cause 503 responses. Use disposable records when retesting write operations. Deactivation changes user-store routing; it does not migrate users.

Passkeys and SSO​

Check HTTPS, browser support, expected origin and fresh challenge for passkeys. For SAML check Entity ID, ACS URL, signing certificate and enabled provider configuration. For SCIM check the workspace token, base URL, Content-Type and supported attributes. See integration availability before treating every 401 as a credential typo.