VS Code: Executed Terminate in stateless workflow means no run history

[John-Bosch]

trafficstars

While using VS Code to run a stateless logic app locally (with run history enabled), having a Terminate action executed in the run means there is no run history displayed. This very simple workflow shows what I mean;

The Terminate is set to return as a success, and the response returns 200, so the workflow appears to run correctly when I use Postman to run it, but no run history is displayed other than the opening request action.

If I make a slightly more complex workflow where I can conditionally execute the Terminate or not, I see the two following results;

In the first, the condition returns false and the Terminate action is processed. In the second the Terminate is bypassed as the condition returns true and the logic app completes normally.

Ignore the scopes, they are there purely as I initially thought it may only be Terminates within Scopes. However, the first screenshot shows this to not be the case.

[hongzli]

Thanks for reporting this -- we have identified it as a bug. The immediate workaround is to change the "AzureFunctionsJobHost__extensionBundle__version" app setting to have value "[1.1.26, 1.1.27)". We are working on a fix that should be deployed within 4-6 weeks, at which point the app setting value change can be reverted.

[John-Bosch]

No worries. Thanks for providing the workaround.

[mark-abrams]

Hi, is there any update for when this issue will be fixed?

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 7 days since being marked as stale.