Skip to main content
Version: 4.0.5


Fix Inventory's resource collection and automated jobs are triggered as part of a series of steps called a workflow. It is possible to create your own automations that hook into the events emitted by workflows.


The workflow command can be used to inspect and run workflows on demand.

collect_and_cleanup Workflow

By default, Fix Inventory triggers the collect_and_cleanup workflow every hour.

The collect_and_cleanup workflow has four steps: collect, cleanup_plan, cleanup, and generate_metrics.


See Events for a list of events emitted by the collect_and_cleanup workflow.


See Workflow Schedules for details on how to configure the schedule of the collect_and_cleanup workflow.


In the collect phase, resources are collected from all configured cloud provider and synchronized with the internal graph.

At the conclusion of this phase, the graph database contains the latest state of all resources.


During the cleanup_plan phase, Fix Inventory computes which resources should be cleaned up, and marks them for deletion during the subsequent cleanup phase.


Fix Inventory ships with built-in cleanup plugins that can be enabled in the fix.worker configuration.


In the cleanup phase, all resources marked for cleanup are deleted if cleanup is enabled.

Resources are deleted in the order mandated by their dependencies and relationships to other resources.


Cleanup is disabled by default. Please refer to Resource Cleanup for details.


As its name suggests, metrics are generated and provided to the time-series database during the generate_metrics phase.

In this phase, Fix Inventory performs several queries to get updated metrics. Since the incoming data will only change during the next collect run, metrics are generated here and cached until the next collection.


You can adjust the metrics that should be generated by editing the Fix Inventory Metrics configuration.

Further Reading