Calling a subflow in foreground that times out while executing on mid the flow ends in state continue_sync when it should end it state error


Description

Calling a subflow in foreground that times out while executing on mid the flow ends in state continue_sync when it should end it state error

Steps to Reproduce

1. Create a mid action that takes some time. You can use this script which will take 1 minute on mid server
(function execute(inputs, outputs) {
var x = Date.now() + 60000;
while (Date.now() < x)
ms.log('sleeping...');
ms.log('finished sleep');
})(inputs, outputs);

2. Create a subflow and add the action as the first step and add a lookup record on problem where problem statement != x for the second step

3. Call the subflow from a background script--
sn_fd.FlowAPI.getRunner().subflow('global.mid_wait_subflow').inForeground().run();

4. After 30 seconds the flow will timeout and the context state will be set to error (Open a chrome incongnito tab to see it). After 60 seconds observe that the context state is changed to continue_sync. The state should remain error.

Workaround

Please see Fixed In versions


Related Problem: PRB1461039