Multi Instance lanes should have timeout limits

Multi Instance lanes should have timeout limits

When a multi-instance step is executed, OO kicks-off multiple instances or lanes, depending on the number of inputs given to the multi-instance step or the throttling value provided. 

During the execution of this step, OO waits for all the currently running lanes to complete. If one or more lane is hung, all the other lanes wait for the hung lanes to complete, essentially making the whole flow going into a hung state.

Having an optional timeout value on lanes will solve this problem as once the timeout is reached for a lane which is taking a lot of time or is hung, the rest of the waiting lanes can proceed to completion.

This is particularly necessary for flows that are performing server reboots, operations across a network, I/O operations, etc in which every lane's behavior can be affected by external factors.

3 Comments
Frequent Visitor.. BlueAnime247
Frequent Visitor..

I completely agree.  What a great idea!

AndreiTruta Outstanding Contributor.
Outstanding Contributor.
Status changed to: Waiting for Votes
 
Micro Focus Contributor
Micro Focus Contributor
Status changed to: Under Consideration

The idea received enough support from the community to be considered for prioritization in our future development planing.

We will continue to monitor the idea so please expect further updates.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.