The current system lacks efficient mechanisms for managing flow history, particularly in environments with numerous flows and versions. This leads to performance issues due to the accumulation of extensive history data. Additionally, the need to update flow IDs on the portal after importing and exporting flows complicates maintenance and disrupts workflow continuity.

Proposed solution is to implement a configurable option within the web configuration file to set a limit on the number of flow history entries retained, defaulting to the latest 10 entries. This setting would allow users to manage performance by controlling the volume of historical data stored.

Furthermore, introduce functionality to safely remove older flow history beyond the configured limit while ensuring the preservation of the flow ID. This would eliminate the need to update flows on the portal after flow re-imports, maintaining consistency and reducing administrative overhead.

These enhancements would significantly improve system performance and administrative efficiency, particularly in complex environments with multiple active flows and versions.