This article exists to provide reasoning and direction when you're seeing more hardware assets in our app versus what you're seeing in one (or more) of your integrations.

Generally team members working out of the RMM/PSA as source of truth will raise this as they're unsure where data in Lifecycle Manager is coming from.

More assets than expected

If you see more assets in Lifecycle Manager than you have in your RMM or PSA tool, here are some possible causes.

1. Do you have more than one Lifecycle Manager integration?
   If your team is seeing one integration, (e.g. RMM) as the source of truth for asset counts, this number will certainly be different to our app if you also have any other integrations added (e.g. PSA, documentation tool, or any networking integrations).
   
   This is because PSAs and Doc Tools often contain assets that can't have an RMM agent installed on them (SANs, VMWare hosts, network, mobile, and imaging assets). Stale data can also commonly sync from PSAs or Doc Tools:

2. Stale data syncing into Lifecycle Manager (old hardware assets)
   While Lifecycle Manager will automatically remove assets or clients that have been marked as inactive in your tools, there may be stale assets syncing into Lifecycle Manager from your integrations that haven't been marked inactive in your tools yet. Once an asset or client is marked as inactive in one of your integrations, it will be removed from our platform.
   
   While this can be done manually, if you are seeing this often it may make sense to review your sync settings between your RMM and PSA so that the PSA and RMM automatically mark inactive devices when devices hit a certain threshold. Check with your RMM/PSA admin as they should be able to help set up a workflow here.
   
   Similarly, if you have an integration with a documentation tool, you should make sure the PSA -> documentation tool sync passes this inactive status over to the doc tool configuration.

3. More RMM assets than managed agent count in RMM
   RMM integrations mainly sync in managed agents, but it's possible assets are syncing into Lifecycle Manager from your RMM that have been discovered over network probe, increasing your asset count. This is an expected part of some RMM integrations.

4. Are your sync settings set up as expected?
   ScalePad Lifecycle Manager syncs assets from your integrations based on your chosen sync settings.
   
   Please review your sync settings and confirm:
   - Whether you're syncing asset types you aren't expecting (unmap them if you have)
   - Whether you've set a last check-in date timeframe to limit syncing of RMM assets (change these settings to your preferred if you have)
   - Whether you're unexpectedly syncing assets without a serial number (change these settings if you have)

Still running into challenges?

We're happy to help! Please open a ticket with us at support@scalepad.com and provide two screenshots as part of your request:

1. An asset that you're seeing in our app that you don't expect to be there
2. A shot of that same asset in your integrations