---
title: Troubleshooting Connections and Sync Issues
description: Symptom-by-symptom fixes for IdP integrations that never complete, missing apps, failed syncs, app connector errors, and emails that do not arrive.
---

[Skip to content](https://support.appgovern.com/knowledge-base/troubleshooting-connections-and-sync-issues#main-content)

English

Show submenu for translations

[Submit a ticket](https://support.appgovern.com/knowledge-base/kb-tickets/new?hsLang=en)

[![AppGovern](https://support.appgovern.com/hs-fs/hubfs/image50-c..jpeg?width=180&height=38&name=image50-c..jpeg)](https://www.appgovern.com/new/)

- [Support home](https://support.appgovern.com/knowledge-base)

Open main navigation

Close main navigation

- [Support home](https://support.appgovern.com/knowledge-base)
- English
  
  Show submenu for translations
- [Submit a ticket](https://support.appgovern.com/knowledge-base/kb-tickets/new)
- [Contact us](https://www.appgovern.com/new/contact/)

[Contact us](https://www.appgovern.com/new/contact/)

 How can we help you?

- There are no suggestions because the search field is empty.

1. [AppGovern Platform Knowledge Base](https://support.appgovern.com/knowledge-base?hsLang=en)
2. [Integrations](https://support.appgovern.com/knowledge-base/integrations?hsLang=en)

# Troubleshooting Connections and Sync Issues

## What to check when apps are missing after an IdP connection, a connector is stuck, or a sync that used to work has stopped.

This article is for when something is not showing up: apps missing after an IdP connection, a connector stuck, or a sync that used to work and stopped. It is organized by symptom.

### Two kinds of connection

AppGovern has two layers of connectivity, and knowing which one is failing saves time:

| Layer | Where | What it does | Health shown as |
| --- | --- | --- | --- |
| IdP integration | Integration \> IDP tab | Pulls users, groups, and the list of apps from Okta, Entra, Google Workspace, JumpCloud, or Auth0 | Completed badge on the card |
| App connection | Application \> App Connections | Connects to an individual app to read its users, map fields, and perform grants | Status and Sync status columns per app |

An app can be discovered through the IdP (layer 1) but still show **Not Connected** at layer 2. That is normal until you set up its connector.

### Reading the App Connections page

Go to **Application \> App Connections**.

![appgovern-app-connections](https://support.appgovern.com/hs-fs/hubfs/appgovern-app-connections.jpg?width=670&height=319&name=appgovern-app-connections.jpg)

Columns to watch:

- **Status**: Not Connected, Connected, or Error. "Not connected yet" means no connector has been configured.
- **Sync status**: Idle, Syncing, or Failed. "No sync in progress" is normal when idle.
- **Sync interval**: Manual or a schedule in hours.
- **Attached groups** and **Access Profile**: whether the app has groups mapped and a JIT access profile. "No Access Profile" means access requests cannot be made for it yet.
- **Comment**: an **Open thread** on each app for owners and admins to leave notes about connection problems.

Click **Connect** to open the four-step wizard: Setup, Connect, Mapping, Segments.

### Symptom: IdP card never shows Completed

**Cause: wrong connection URL or client ID.** Open Edit on the card and check both against the app you registered in the IdP. For Entra, the URL must include your tenant ID. For Okta, use your org URL, not the admin URL.

**Cause: missing permissions or scopes.** Authorize can succeed at the OAuth level and still fail to read data. Check the required scopes in [Connecting Your Identity Provider](https://example.com/#) and confirm admin consent (Entra) or the admin role (Okta).

**Cause: wrong key format (Okta).** The private key must be the JWK JSON or PEM that matches the Key ID. Pasting the public key is a common mistake.

### Symptom: IdP is Completed but no apps appear

**Cause: first sync still running.** Wait for the sync interval, then refresh App Directory. Large directories can take a while on the first pass.

**Cause: the IdP app can read users but not applications.** Entra needs Application.Read.All and ServicePrincipal permissions; Okta needs okta.apps.read. Add the permission, re-consent, and sync again.

**Cause: apps exist but are filtered.** On App Directory, reset the SSO, Status, and Sources filters and check the All Apps tab.

### Symptom: sync worked before and now shows Failed

**Cause: expired secret.** Entra client secrets have an expiry date you chose at creation (often 6 or 12 months). Create a new secret in Entra, open Edit on the Azure card, paste it, and Authorize again.

**Cause: revoked OAuth grant.** For Google Workspace, an admin may have revoked the OAuth client or changed the authorizing account. Re-authorize from the GWS card.

**Cause: rotated key.** If someone generated a new key pair in Okta, the old Key ID no longer validates. Update both the private key and Key ID.

**Cause: rate limiting.** Very large tenants can hit IdP API limits. Increase the sync interval so runs are less frequent.

### Symptom: app connector fails to connect

**Cause: wrong authentication type.** The connector supports API Key, Bearer Token, Basic Auth, Username/Password, and Session Cookie. Match what the app's API expects. The API key is validated when you click Test Connection.

**Cause: saved credentials reused.** On edit, a saved key stays masked and is reused unless you enter a new one. If the key was rotated, paste the new value; leaving the field untouched keeps the old one.

**Cause: IP allowlisting on the app side.** Some SaaS admin APIs restrict callers by IP. Add AppGovern's egress addresses to the app's allowlist. Contact support for the current list.

**Cause: no marketplace connector.** If the app is not in the connector marketplace, use Custom Connector with the app's REST API, or choose No Connection (Manual Import) and upload users as CSV.

### Symptom: users are synced but managers or departments are empty

Manager and department come from the IdP user attributes. Confirm the attributes are populated in the IdP and that the integration has permission to read them (Okta: okta.users.read; Entra: User.Read.All). Local users need these set by hand under User Management.

### Symptom: NHI detection is not running

Go to **Non-human & AI Identity \> Settings \> Governance** and check that **Enable scheduled bot detection sync** is on. The Detection health panel shows the last and next cron run. If HRIS comparison is expected but mode shows "regex-only," no HR source is configured under Data Sources.

### Symptom: certification emails are not arriving

- Check **Settings \> SMTP** if you use your own mail server; a failed SMTP test means nothing goes out.
- Confirm the recipient has an email address on their user record. IdP users without an email attribute cannot receive mail.
- Check the reminder settings under Access Certification Settings; if Max reminders is 0, only the initial request is sent.
- Ask the recipient to check spam and allowlist the sender address shown under Tenant Settings \> Notification Email.

### Where to look for detail

- **Insights & Compliance \> Activity Stream**: a running log of sync events and connector activity.
- **Insights & Compliance \> Audit Log**: who changed what and when, including integration edits.
- The **Open thread** comment on each app connection, for notes from whoever last touched it.

### Still stuck

Send support the following and it will be resolved faster: the integration or app name, the exact error text, the time of the last successful sync, and what changed on the IdP side recently (secret rotation, permission changes, admin account changes).

- [Getting started](https://support.appgovern.com/knowledge-base/getting-started?hsLang=en)
- [Integrations](https://support.appgovern.com/knowledge-base/integrations?hsLang=en)
- [Application Governance](https://support.appgovern.com/knowledge-base/application-governance?hsLang=en)
- [Access Certification](https://support.appgovern.com/knowledge-base/access-certification?hsLang=en)
- [Non-Human & AI Identity](https://support.appgovern.com/knowledge-base/non-human-ai-identity?hsLang=en)
- [Access Hub](https://support.appgovern.com/knowledge-base/access-hub?hsLang=en)
- [AI Workforce Governance](https://support.appgovern.com/knowledge-base/ai-workforce-governance?hsLang=en)
- [Settings](https://support.appgovern.com/knowledge-base/settings?hsLang=en)

- [Support home](https://support.appgovern.com/knowledge-base)
- [Contact us](https://www.appgovern.com/new/contact/)
- [AppGovern.com](https://www.appgovern.com/new/)
- [Trust Center](https://www.appgovern.com/new/why/trust-center/)
- [Privacy](https://www.appgovern.com/new/legal/privacy/)
- [Terms](https://www.appgovern.com/new/legal/terms/)

[![AppGovern](https://support.appgovern.com/hs-fs/hubfs/image50-c..jpeg?width=250&height=52&name=image50-c..jpeg "AppGovern")](https://www.appgovern.com/new/)

AppGovern is the Ownership-Driven Security platform. Find and manage every app and every identity: humans, AI agents, and service accounts. See what each one reaches. Have a named owner accept accountability for it.

Copyright © 2026, AppGovern Corp.