Skip to main content

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

IT Glue and Liongard are out of sync. On the Admin > Integrations screen, use the troubleshooting dropdown to "Sync Mappings" and then re-run the inspector. If the issue persists, please contact support.

Overview 💥

Partners may encounter the following error when using the IT Glue integration:

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

Reference :

This issue occurs when mapping relationships between Liongard inspectors and IT Glue Flexible Asset Types become misaligned, modified, or invalid.

Impact 🥶

  • Inspectors fail with Platform Failure

  • Data is not created or updated in IT Glue

  • Flexible Assets stop syncing

  • Multiple inspectors across environments may be affected

Why This Happens 🤔

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

  • Liongard uses predefined mappings to sync inspector data into IT Glue Flexible Asset Types.

  • If those mappings are changed or broken, synchronization fails.

🔍 Common Causes

Cause

Explanation

✏️ Manual Mapping Changes

Flexible Asset Type mapping modified (e.g., changed to incorrect type like “Serversus”)

🔗 Incorrect Asset Type Mapping

Inspector mapped to wrong or non-existent Flexible Asset

❌ Deleted / Renamed Asset Types

Required Flexible Asset Types removed or altered in IT Glue

🔄 Broken Sync Relationships

Mapping exists but no longer aligns with expected schema

⚙️ Partial or Failed Mapping Updates

Changes applied incorrectly or incompletely

What the Error Really Means? 🧐

👉 The error indicates:

  • Liongard attempted to sync data

  • IT Glue mapping does not match expected structure

  • Flexible Asset Type or fields cannot be found

➡️ Result: Sync fails and inspectors report “out of sync”

How Data Flow Works 🔄

Inspector → Dataprint (JSON)
        ↓
Mapping Layer (Flexible Asset Mapping)
        ↓
IT Glue Flexible Asset Type

❌ Broken mapping → Sync fails
✅ Valid mapping → Data updates successfully

Steps to Resolve 🧑‍🏫

Step 1 — Run Sync Actions

Navigate to:

  • Admin → Integrations → IT Glue → Flexible Assets

Run:

  • Repair

  • Re-sync

  • Sync Mappings

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

Reference:

Step 2 — Validate Flexible Asset Mapping

Navigate to:

  • Admin → Integrations → IT Glue → Flexible Assets → Liongard Flexible Asset Types

  • Ensure the Flexible Asset Auto-Updating is enabled for Liongard Flexible Asset Type(s) , Example :Cloud Productivity (auto), which is the Flexible Asset for Microsoft 365 & Google WorkSpace. Inspector.

Navigate to:

  • Admin → Integrations → IT Glue → Flexible Assets → All IT Glue Flexible Asset Types

  • Locate the affected Flexible Asset type, Example : Cloud Productivity (auto), which is the Flexible Asset for Microsoft 365 & Google WorkSpace Inspector.

Check:

  • Correct Asset Type is selected {e.g., Cloud Productivity (auto)not custom/incorrect names}

  • Mapping exists for affected inspectors

  • No unexpected or modified mapping names

Step 3 — Identify Incorrect Mapping (Primary Root Cause) 🔍

Look for:

  • Incorrect mapping names {e.g., Cloud Platform instead of Cloud Productivity (auto)}

  • Custom or altered asset types

  • Missing or mismatched mappings

👉 Even a small change in mapping name/type may break sync.

Step 4 — Recreate Correct Mapping (Primary Fix) 🔧

If mapping is incorrect or modified:

  1. Remove the incorrect mapping

  2. Save changes

  3. Run:

    • Repair

    • Force Repair

    • Re-sync

Step 5 — Re-run Inspectors

👉 This ensures fresh data sync with corrected mapping

Step 6 — Verify in IT Glue

In IT Glue:

  • Navigate to Flexible Assets

  • Confirm:

    • Assets are being created

    • Existing assets are updating

    • Correct asset type is used {e.g., Cloud Productivity (auto)}

Expected Result ✅

  • Inspectors run successfully

  • No “out of sync” errors

  • Flexible Assets are created/updated correctly

  • Mapping aligns with Liongard defaults

Example 🙋‍♂️

  • Mapping was modified from Server (auto) → Serversus

  • This broke sync for:

    • Windows Server inspectors

    • Linux inspectors

✅ Fix:

  • Restored correct mapping (Server (auto))

  • Re-ran inspectors

  • Sync resumed successfully

  • Issue Resolved

When This Issue Commonly Occurs 🤷🏻‍♂️

  • Manual edits to Flexible Asset mappings

  • Custom naming or restructuring in IT Glue

  • Reconfiguration of integration

  • Partial or incorrect mapping updates

  • Multiple admins modifying mappings

Troubleshooting Checklist 📋

Check

Expected Outcome

Run Sync Mappings

Attempts mapping refresh

Verify Asset Type Mapping

Correct mapping in place

Remove Incorrect Mapping

Clears broken reference

Recreate Mapping

Restores correct structure

Re-run Inspectors

Confirms resolution

Check IT Glue Assets

Data syncing properly

When to Contact Support 🦁

Contact Liongard Support if:

  • Issue persists after mapping reset

  • Multiple mappings appear broken

  • Flexible Asset Types are missing entirely

  • Sync still fails after correct mapping is applied

Provide:

  • Inspector names

  • Affected asset types

  • Screenshots of mapping configuration

  • Error message/logs

Key Takeaway 💡

This issue is caused by incorrect or modified IT Glue mapping — not by inspector failure.

  • ✔ Most commonly caused by mapping changes or incorrect asset types

  • ✔ Resolved by restoring correct Flexible Asset mappings

Summary 🚀

  • Error occurs due to mapping mismatch between Liongard and IT Glue

  • Inspectors fail because expected asset types or fields are missing

  • Fix involves:

    • Removing incorrect mappings

    • Recreating correct default mappings

  • Once corrected, sync resumes normally

Did this answer your question?