Overview π₯
Liongardβs IT Glue integration allows Inspector data to sync automatically into Flexible Assets for documentation and visibility. In some cases, Flexible Assets may not sync correctly, appear incomplete, or stop updating altogether.
This article explains:
Common causes of Flexible Asset sync issues
How to identify and resolve mapping problems
When to repair or remove mappings
When to contact Liongard Support
Common Symptoms π€
You may be experiencing a Flexible Asset issue if:
Flexible Assets are not appearing in IT Glue after an Inspector run
Assets appear partially populated or outdated
Only one Environment is affected
Errors appear in the Flexible Asset mapping screen
Why Does This Happen? π€
Flexible Asset sync issues typically occur due to one or more of the following reasons:
Cause | Description |
Mapping corruption | Flexible Asset mappings can become misaligned after integration changes |
Disabled Environment toggle | The Environment is not enabled for Flexible Asset syncing |
Inspector failure | The Inspector did not complete successfully |
API or permission errors | IT Glue API access issues prevent asset creation or updates |
Integration changes | Recent updates to IT Glue or Liongard settings |
Steps To Resolve π¨βπ»
Step 1: Verify Flexible Asset Mappings
Navigate to Admin β Integrations β IT Glue β Flexible Assets
Locate the Flexible Asset type you are troubleshooting
Check for error indicators on the mapping
If you see an error on the mapping, proceed to Step 2.
Step 2: Repair the Mapping
From the Flexible Assets screen:
After the repair completes, re-run the affected Inspector,
Step 3: Remove and Recreate the Mapping
If repairing the mapping does not resolve the issue:
On Flexible Assets page β Liongard Flexible Asset Types.
Click Remove Mapping.
Re-run the Inspector.
β οΈ Removing a mapping does not delete existing data in IT Glue but resets how future data is synced.
Step 4: Verify Environment-Level Settings
If the issue only affects one Environment:
Open the Environments tab within the Flexible Assets screen
Confirm the toggle for "Flexible Asset Auto-Updating" is enabled for the affected Environment.
Re-run the Inspector again after making changes to verify the status.
Step 5: Check Inspector Health
Ensure the Inspector responsible for the data:
Completes successfully.
Does not show any failures.
If the Inspector fails, resolve that issue first before troubleshooting Flexible Assets further.
Additional Validation Checklist π
Check | Action |
IT Glue API credentials | Verify credentials are valid and unchanged |
Organization mapping | Confirm the correct IT Glue organization is mapped |
Recent integration changes | Review any recent updates or repairs |
Inspector scheduling | Ensure Inspectors are running as expected |
When Should You Contact Support? π¦
Contact Liongard Support if:
Flexible Assets fail to sync after repairs and re-runs.
You see persistent API errors.
Providing screenshots of the Flexible Asset mapping screen and Inspector run status will help speed up troubleshooting.