Skip to main content

Troubleshooting

Use this page when a setup step fails or a live workflow does not behave as expected. Start from the affected app, then use the service page and audit logs together.

Fast diagnosis path​

  1. Confirm you are in the correct app.
  2. Read the app overview state.
  3. Open the affected service.
  4. Check whether the page shows setup, ready, live, or needs attention.
  5. Check audit logs for recent changes.
  6. Test with a single user, endpoint, or message.
  7. Fix the smallest confirmed issue first.
Switera app overview with readiness and next action cards
The app overview is the best first stop because it points to missing organizations, Auth gaps, and integration setup issues.

Login or registration fails​

Check:

  • the app has a sign-in method enabled
  • email verification policy is intentional
  • provider credentials are correct
  • redirect URI matches exactly
  • user is not banned or suspended
  • MFA requirement matches the user state
  • session policy is not forcing an unexpected step
  • hosted Auth branding and legal settings do not block the flow

Next pages:

Invitations are not accepted​

Check:

  • organization exists
  • invitation was sent to the correct address
  • invitation is not expired or revoked
  • email route test succeeds
  • invitation template contains a valid accept link
  • recipient is not suppressed
  • first member has the intended role

Next pages:

Email does not send​

Check:

  • sender profile is complete
  • sender domain is verified when required
  • route test works
  • template is active
  • recipient is not suppressed
  • runtime history shows queued, sent, bounced, or failed state
  • built-in email is enabled when the workflow depends on it

Next pages:

Webhook delivery fails​

Check:

  • endpoint URL is HTTPS
  • endpoint is enabled
  • endpoint is subscribed to the event type
  • receiver returns a success HTTP status quickly
  • receiver validates the current endpoint secret
  • delivery attempts show the expected response code
  • slow work is handled asynchronously by the receiver

Next pages:

API call returns unauthorized​

Check:

  • secret key is present
  • key belongs to the correct app
  • key belongs to the correct environment, test or live
  • backend is using the current rotated key
  • key is not accidentally quoted or truncated
  • frontend code is not trying to use a secret key

Next page:

Wrong app was configured​

If a setting was changed in the wrong app:

  1. Stop making changes.
  2. Open the correct app and compare settings.
  3. Open Admin > Audit Logs in the wrong app.
  4. Identify the exact change.
  5. Revert the wrong setting manually if safe.
  6. Rotate affected credentials if they were exposed or used in the wrong environment.
  7. Document the correction for your team.

Escalation checklist​

When escalating an issue internally, include:

  • app name
  • affected organization when relevant
  • timestamp and timezone
  • user-visible error message
  • affected service page
  • relevant audit event IDs
  • webhook delivery ID or email message ID when relevant

Do not include passwords, provider secrets, API secret keys, private tokens, or unnecessary personal data.