Troubleshooting
An integration is failing — what to do
Read the error, in order: the card status, the error list behind the count, then Test. Most causes are a rotated key or a permission change.
Read the card first
Open Integrations. Each card carries three facts, and they mean different things:
| What you see | What it means |
|---|---|
| Status active, recent Last sync | The integration is working. If devices still look wrong, the problem is scope or grouping, not connectivity. |
| Status active with an error count | Some calls are failing while others succeed — often one endpoint or one site, or rate limiting. Frequently transient. |
| Status Error — needs attention | Repeated failures. The key, its permissions or the account behind it is the usual cause. |
| Last sync: never | No successful poll has ever run. Almost always a bad key, or a key of the wrong kind. |
Then read the actual errors
- 1Click the error count on the card. It opens a list of the individual errors recorded over the last 14 days, newest first, with the status code and the endpoint that failed.
- 2Use Save as .txt if you want to send it on.
- 3Press Test to make a fresh call right now and see the current result.
An empty error list does not always mean there were no errors. Individual errors have only been recorded since that feature shipped — an integration that failed before then shows a count with no detail behind it. The modal says which case you are looking at; a list that says "could not be loaded" is a failed query, not a clean bill of health.
Common causes, in the order they actually occur
| Symptom | Usual cause | Fix |
|---|---|---|
| 401 / 403 on every call | The key was revoked, rotated, or belongs to a user whose access was removed. | Generate a new key and remove and re-add the integration. |
| Ubiquiti: last sync never, key looks right | It is a console-local Network API key, not a Site Manager key. | Create the key at unifi.ui.com instead — see Connect Ubiquiti UniFi. |
| Domotz: permission or not-found errors | Wrong regional API cell. | Set API base URL on the integration to your account’s cell — see Connect Domotz. |
| 429, or errors that come and go | Vendor rate limiting. | Usually self-correcting. If it persists, reduce what the integration syncs with Scope. |
| Some sites sync, others do not | The key’s account cannot see those sites, or they are scoped out. | Check Scope, then check the account’s permissions at the vendor. |
Connected fine, but no devices
- Give it a minute — polling runs every minute, but the first cycle after connecting has the most to do.
- Check Scope: if the integration is set to Only what I select and nothing is selected, it is working exactly as configured and importing nothing.
- Check at the vendor that the devices are adopted, online and visible to the account the key belongs to. StatusCheck can only see what the API returns.
Rotating a key is safe at any time. Remove the integration and add it again with the new key — choosing to keep the devices means their history is preserved.
Still stuck? Save the error list to a .txt file and send it to hello@statuscheck.dev with the integration label. That file contains the status codes and endpoints we need and no credentials.
Related
Did this miss something? Tell us — support is a small team and the fastest fix is usually a better article.