My sync didn't run

If you expected a sync to occur and it did not, work through the following checks in order. They are arranged by likelihood.

1. Confirm the sync did not produce changes

The most common cause of an apparent missing sync is a successful run that produced no diff. Open the integration detail page and check the Last sync timestamp. If it is recent, the sync ran successfully and detected no changes — there is nothing wrong.

2. Authentication failures

If the specification is hosted behind authentication and the sync returns a 401 or 403, the credentials Intello stores may have rotated, expired, or had their permissions revoked.

Open the dependency at Dependencies → [integration] → Edit, locate the Authentication field, and re-enter the credential. The next scheduled sync will pick up the new credential.

If the sync still fails after a credential update, the credential likely lacks permission to read the specification endpoint. Coordinate with whoever administers vendor access at your organization.

3. Vendor-side errors

If the vendor's specification endpoint returns 5xx errors or times out, syncs will fail until the endpoint recovers. Intello retries automatically on the regular cadence; in most cases, the integration recovers without manual intervention. If the failures persist, the spec URL itself may have moved.

4. Rate limiting

If a vendor returns 429 responses, Intello backs off and reduces cadence to remain within their rate limits. The sync history will record these as rate-limited attempts. Cadence returns to normal once the vendor's rate-limit window resets. If the issue persists, contact the vendor about a higher rate limit on their specification endpoint.

5. Health-status pause

After ten consecutive sync failures, Intello transitions the dependency to a paused health state. The scheduler stops enqueuing automatic syncs to avoid wasted load until the underlying issue is resolved; the dependency resumes automatically once the upstream issue is corrected and the next scheduled sync succeeds. The integration's health status is visible on the dependency detail page.