OneView history retention
After the data is delivered to all modeled targets in a data flow and all started instances of any defined BPMS models have finished, the timeline for that data is considered “Complete.” Before that point, the timeline is considered “In Flight.” It is feasible that a data timeline could remain “in flight” indefinitely, for example, if users do not complete sent notifications or integrations errors are assigned an action but not marked as handled by administrators.
The OneView history retention – Complete value is the time that completed timelines are kept in the active OneView search index. After that time, they are archived to long-term storage, where selected messages for a time window can be temporarily restored.
The OneView history retention - In Flight value is the time that in-flight timelines are kept in the active OneView search index. After that time, they are archived to long-term storage, where selected messages for a time window can be temporarily restored.
Optionally, archived data can be permanently purged if you need to increase storage space.