Inspector(s) | Error: ConnectWise and Liongard Are Out of Sync

Overview 💥

Partners may encounter the following error when running inspectors integrated with ConnectWise:

“ConnectWise and Liongard are out of sync. On the Admin > Integrations screen, use the troubleshooting dropdown to ‘Sync Mappings’ and then re-run the inspector.”

This issue typically occurs when configuration mappings between Liongard and ConnectWise become invalid, outdated, or misaligned.

Impact 🥶

Inspectors fail with status as "Platform Failure"
Data cannot sync to ConnectWise configurations
Errors related to missing mapped fields
Integration appears connected but is functionally broken

Why This Happens 🤔

This is a mapping integrity issue, not an inspector or credential failure.

🔹 Root Cause

Liongard relies on field mappings to sync inspector data into ConnectWise Configuration Types.

If those mappings break, Liongard cannot find the expected fields.

🔍 Common Causes

Cause	Explanation
🕒 Outdated / Legacy Configurations	Integration was disabled for long periods (e.g., months/years), causing schema drift
🔄 Re-enabled Old Integration	Old mappings reference fields that no longer exist
✏️ Changes in ConnectWise Configurations	Fields renamed, removed, or modified
❌ Deleted or Missing Fields	Required fields no longer exist in ConnectWise
🔗 Broken Mapping Relationships	Mapping still exists but points to invalid structure

What the Error Really Means? 🧐

Example error from logs:

Unable to find mapped fields "Total Devices", "Active Users Without MFA", "Directory Name"...

👉 This means:

Liongard is trying to sync data
ConnectWise no longer has those mapped fields
The mapping is stale or invalid

How Data Flow Works (Simplified) 🔄

Liongard Inspector → Data (Dataprint)
        ↓
Mapping Layer (Field Matching)
        ↓
ConnectWise Configuration Type

❌ If mapping layer breaks → Sync fails
✅ If mapping is valid → Data syncs successfully

Steps to Resolve 🧑‍🏫

Step 1 — Attempt Basic Sync Repair

Navigate to:

Admin → Integrations → ConnectWise → Configuration Types

From "Troubleshooting" dropdown menu Run:

Repair
Force Repair
Re-sync

👉 Then Re-run the affected inspector (Clear Cache + Debug recommended).

Reference:

Step 2 — Validate Configuration Type Mapping

Navigate to:

Admin → Integrations → ConnectWise → Configuration Types → Liongard Configuration Types
Ensure the Configuration Auto-Updating is enabled for Liongard Configuration Type(s) , Example :Cloud Productivity (auto), which is the configuration for Microsoft 365 & Google WorkSpace. Inspector.

Navigate to:

Admin → Integrations → ConnectWise → Configuration Types → All ConnectWise Configuration Types
Locate the affected configuration type, Example :Cloud Productivity (auto), which is the configuration for Microsoft 365 & Google WorkSpace Inspector.

👉 Check for:

Missing fields
Incorrect mappings
Empty or broken field associations

Step 3 — Reset Mapping 🔧

If mappings appear broken:

Remove the affected mapping completely
Save changes
Run:
- Repair
- Force Repair
- Re-sync

👉 This forces Liongard to rebuild mappings

👉 Then re-run the affected inspector. If the issue persists, continue with Step 4

Step 4 — Resolve Legacy Configuration Issues (Critical) 🚨

👉 The problem is likely stale ConnectWise configuration records

⏯️ Fix: Rename Configuration in ConnectWise

In ConnectWise Manage:

Navigate to:
System → Setup Tables → Configurations
Search for the affected configuration
Open the configuration record
Rename it (example):
Old Name → Old Name (Legacy)
Click Save
Repeat Step 1

If the problem is still not resolved and a similar ConnectWise-related error appears, please proceed to Step 5.

Step 5 — Delete Old Configuration From ConnectWise (Optional)

In ConnectWise Manage:

Navigate to:
System → Setup Tables → Configurations
Search for the affected configuration
Delete the affected configuration.
Repeat Step 1

Why This Works 🤷🏻‍♂️

Renaming forces ConnectWise to:

Refresh internal references
Break linkage to outdated mappings
Allow Liongard to create a fresh mapping relationship

Expected Result 🧑‍💻

Inspector runs successfully
No “out of sync” errors
Data syncs correctly into ConnectWise
New mapping aligns with current schema

When This Issue Commonly Occurs 🧑‍🏫

Integration disabled for long periods (e.g., since 2022 → re-enabled later)
Reusing old ConnectWise configurations
Schema changes in ConnectWise over time
Initial testing environments later reused in production

Troubleshooting Checklist 📋

Check	Expected Outcome
Run Sync Mappings	Mapping refresh attempt
Remove & Recreate Mapping	Clears invalid relationships
Rename Configuration in ConnectWise	Breaks stale references
Delete Old Configuration Records from ConnectWise (optional)	Avoid confusion and reduce the likelihood of Liongard-ConnectWise integration sync failures.
Re-run Inspector (Debug Mode)	Confirms fix
Review Logs for Missing Fields	Identifies mapping gaps

When to Contact Support 🦁

Contact Liongard Support if:

Issue persists after mapping reset + rename & deletion
Errors continue showing missing fields
Multiple configuration types are affected
You cannot identify which mapping is broken

Provide:

Inspector name(s)
Error message / Inspection logs
Configuration Type name
Confirmation of steps performed

Key Takeaway 💡

This is not an inspector issue — it is a mapping mismatch between Liongard and ConnectWise.

✔ Most commonly caused by legacy or stale configurations
✔ Resolved by resetting mappings and refreshing ConnectWise configuration references.

Summary 🚀

Error occurs due to invalid or outdated field mappings
Basic repair steps may not resolve deeply stale mappings
Renaming ConnectWise configurations is often the key fix
After refresh, Liongard rebuilds correct mappings automatically