What creates multiple History Sets in sys_history_set table?

[ddykhoff]

I know that they are created dynamically when the information is requested, and that is fine, but why would more than one history set need to be created at a time? What situations cause this to happen?

Is it safe to use the most recently updated history set (i.e. the one with the latest last_update_recorded value), or do different history sets contain different sets of information?

[Daniel Pettet]

Most likely a report could cause this.

Normally the history set is only generated when the user first views the record. Perhaps there is some script or logic pre-building some history sets for performance reasons. Eg. Reporting on audit info. There is an API for managing history but it's not publicly exposed. More information would be available via a Hi support request.