Skip to main content
Sometimes a connection you’ve already set up stops working: an OAuth sign-in expires, an API key gets rotated on the provider’s side, or a step just never got finished. Credential Recovery is how Airia notices that for you and gets you back to a working connection in a click, instead of leaving you to figure out which app broke and why.

What Can Trigger It

A connected app can end up needing recovery for a few reasons:
SituationWhat Happened
Never connectedYour organization has this app available, but you haven’t signed in or provided your own credentials yet.
Needs your sign-inAn admin already configured this app for your organization, but you still need to connect your own account to use it.
No longer validYou were connected, but your sign-in expired, was revoked, or the app’s credentials were rotated on the provider’s side.
Airia automatically refreshes OAuth sign-ins behind the scenes well before they expire, so in most cases you’ll never notice anything. Recovery only comes into play when that automatic refresh isn’t possible, most often because access was revoked or changed outside of Airia.

What You’ll See

Where the connection is being used determines how you’re notified:
  • In Airia Chat, a banner appears above the chat box calling out exactly which app needs attention, with a button to fix it right there.
  • In an external AI tool (like Cursor or Claude Code) connected through an MCP Gateway, the assistant’s response will include a link explaining that a specific tool needs reconnecting, along with a URL you can use to fix it.
  • On the Your Integrations page, the affected app’s status shows as Connect to use or Needs setup so you can spot and fix it any time, even if you didn’t get a banner.
A broken connection only affects that one app. Everything else you’ve connected keeps working normally, and the rest of your chat session or tool call isn’t interrupted.

Fixing It

Recovery is designed to take one click:
  1. Click Connect (or the link you were given).
  2. Sign in again, or provide a new API key if that’s how the app authenticates.
  3. Once it succeeds, the banner clears and the app is ready to use again immediately, no need to retry your original request from scratch.
If you were sent to the Your Integrations page through a recovery link, that page opens with the affected app already in focus so you don’t have to hunt for it. Click Browse all integrations if you want to see the rest of your catalog instead.
Before you finish reconnecting, Airia shows you the exact permissions the app is requesting, the same as any other sign-in, so you can confirm nothing has changed.

Personal Connections Only

Credential Recovery applies to your own personal sign-in or key for an app, not to shared, Tenant-level configurations an admin set up. If a Tenant-level connection itself stops working, that’s on your admin to fix; see Tenant vs. Personal Level App Credentials for how the two relate. If several of your connected apps share one underlying sign-in (for example, multiple Google tools), reconnecting once clears recovery for all of them.

Where to Manage This

Everything described here happens through Your Integrations at https://airia.ai/gateway/mcp-self-service. You can always check the status of your connections there, whether or not you’ve been prompted by a recovery banner.