Troubleshoot common problems

Start with the displayed state

1. Read the complete message and identify the affected record, provider, or setup step.
2. Confirm the account, workspace, role, and location are correct.
3. Open the relevant settings area and check saved values, prerequisites, and provider status.
4. Retry only after correcting the cause; repeated requests can trigger rate limiting.
5. If the action remains blocked, preserve the time, route, safe reference ID, and steps taken for support.

Common causes

• Authentication expired, wrong identity, missing invitation, or insufficient role/location access.
• Onboarding section incomplete, stale validation evidence, or a department without a destination.
• Disconnected provider, missing permission, invalid callback/webhook, stale token, or failed initial sync.
• Calendar closure, blocker, buffer overlap, hold, capability mismatch, or booking disabled.
• Stripe account incomplete/restricted, payment not verified, mismatched workspace/account, or failed reconciliation.
• Telephony route not activated, no status callbacks, invalid destination, exhausted fallback, or provider outage.

Rate limits and retries

A 429 response means the relevant service is rate limiting requests. NevoDesk should preserve submitted configuration, apply backoff, and avoid repeatedly invoking the same provider-dependent modeling or action. If a local save can complete without the external model, the product should clearly distinguish the saved result from provider-generated enrichment.