Support Surface

Public help content lives at the Support root; operator-only diagnostics stay behind platform roles.
Workspace users can reach help and contact paths without seeing Hangfire or worker-status tooling.

Reliability and troubleshooting

Handle repeated auth failures before they become an outage

Credential issues now fail closed more cleanly, but operators still need a repeatable response path when an account stops authenticating.

Article

First response

Do not immediately assume the worker is broken. Repeated auth failures usually start with the account itself. Check whether credentials are missing, revoked, or simply out of date.

  • Open the affected account in the Accounts area.
  • Review the last credential check and account error state.
  • Update the stored password or provider credentials before re-enabling.

Article

Escalation threshold

Escalate after you have verified the credentials, the provider settings, and the workspace activity state. Include that verification in the support request so the ticket does not bounce back for basic repro details.

  • Mention when the account last worked correctly.
  • Mention whether the failure started after a provider-side policy change.
  • Use billing/contact routing only if the root issue is account access policy, not mailbox configuration.

Related Articles

Keep reading

Open full help center
Read queued and failed work before escalating Workspace operators and support agents

The app now exposes queued and failed work so users and support agents can start with real runtime state instead of only raw anecdotes.

Read article