@ssakunala Is BFI supposed to create a new Scanner Catalog Distribution (Version: xxxxxxx.y) action every time the import runs? The Version number is the same for each action, so it appears to be a duplicate of the previous action. The previous day’s action is stopped, so this is mostly a matter of console hygiene.
The action should not be submitted with each import. I had the automated catalog download setting disabled. Running an import with it’s enabled. Will confirm in few minutes
@itsmpro92 Hi Byod, I see the same issue as you are seeing. I ran imports and see the task with same catalog version is being submitted. Please open a support case. I will also submit an internal ticket.
Thank you for reporting this issue.
1 Like
I’ve opened case CS1405892 for this issue.
I saw the update in the case that the latest successful catalog import into BFI resolved this issue. I have sent the same update to our BFI team. Thank you
@ssakunala I'm resurrecting this thread because the action is being stopped and created on every import run with BFI Version: 11.0.7.0-20260318-1628.
Possibly related: a scheduled import failed when the SQL Server was rebooted after patching earlier this month. The connection was reestablished when the BFI server was restarted (after patching). Since then, the ToDo List includes:
Fix the catalog import problem.
Catalog import failed on 06/22/2026 01:00 AM.
Last successful catalog import 05/05/2026 03:04 PM
The import process has run succesfully many times both before and after 6/22, so I'm not sure how to clear this To Do item. I have restarted the BFI service, and run a manual import. They did not clear the issue.
Hi Brad,
Sorry to hear that the issue is still happening. Have you opened a new support ticket? Take screenshots of the catalog info and upload them to the case.
Also check if the “Server Software Catalog Update” task from BigFix Inventory Discovery site is relevant. If so take action to download the catalog. The next Import will process the new catalog. Confirm that the catalog processing is successful.
I've opened case CS1456523.
I previously deployed the newest catalog two days after it showed as relevant. No catalog task is relevant at the moment.