Reconnect after a credential alert

Once a Provider Credential that used to work stops authenticating, your Stack's control plane emails your tenant admin a link to fix it — this page is what to do when that email arrives. See Auth & consent for what a Credential actually is and why re-affirming its health happens by ordinary use, not a separate check-in.

Steps

1. Open the link in the email. It's shaped like <control-plane-url>/v1/handoff/start?next=%23%2Fauth — if you're still signed in to the control plane, it lands you straight on your Dashboard's Auth page (#/auth); if you're signed out, you'll hit the control-plane sign-in gate first, then land on the same place.
2. Find the Provider whose badge reads invalid (not merely "not authenticated" — that's a Credential your Stack has on file but can no longer use, distinct from one never provisioned at all).
3. Reconnect it the same way you connected it the first time:
   • An expired or revoked vendor API key — paste a fresh one under Auth.
   • An expired personal-subscription token or auth file — see Connect a personal subscription credential for the consent-checkbox step that path requires.

Why this only ever emails once per problem

You'll get exactly one email per Credential per transition into "invalid" — not one every time the control plane happens to notice it's still broken. Fixing it re-arms the alert, so a later relapse emails you again; nothing about this depends on you dismissing or acknowledging the email itself.

Related

• Auth & consent — what a Credential is and how its health is established.
• Connect a personal subscription credential — the consent step for an OAuth token or an auth file.
• Quickstart — connecting a Provider for the first time with a vendor API key.