Expected outcome
The affected connection is restored or escalated with enough context for the onboarding team to diagnose it.
Tempera is in private preview and provides private APIs across its product areas. Access is arranged through onboarding for an agreed evaluation, with product-specific credentials, endpoints, and environment details supplied directly to your team. API maturity ranges from preview to research, and no shared cross-product endpoint is implied.
Before you start
- The affected client name and its visible connection state
Steps
- 01
Read the connection state
Identify whether the connection is expired, revoked, missing a permission, or configured for the wrong workspace.
- 02
Fix only that state
Reconnect an expired client, request the specific missing permission, or switch to the intended workspace.
- 03
Repeat one narrow check
Run the smallest read-only task that proves the connection works.
- 04
Escalate with safe context
Share the client, workspace label, time, state, and request identifier. Do not include a token, key, or browser credential.
What success looks like
- The user understands why the connection is blocked.
- The recovery step does not add unrelated access.
- Any escalation contains useful context without secret material.
If something is blocked
- If the state is unclear, stop repeated retries and contact the onboarding team with the safe context above.
- If reconnecting selects the wrong workspace, sign out of that client and restart from the intended workspace.
- If a key was exposed while troubleshooting, revoke it before continuing.