Why it happens
A restricted key or token was rotated, expired or revoked at the provider, and nothing that reads through it can read any more.
How to tell
- Integrations shows the credential as rejected.
- A coverage gap opened on the app, naming what can no longer be observed.
- The provider's audit log shows the key deleted or rotated.
The fix
- Create a new read-only key at the provider, with the same minimal scopes as before.
- Paste it under Integrations › the provider › Manage. Coverage returns on the next check.
How Keelnest catches it
Every connected credential is checked on each run. A rejected one opens a coverage gap that says what is now unknown — never painted red, because an app nobody can read is not an app that is down.
Know the moment this happens.
Keelnest watches your production app every five minutes and tells you in plain English what broke — with the fix. Free for your first app.