I tried this:

I ran two versions of a workflow:

In the first workflow, the workflow ended with a non-nested block.

In the second workflow, the workflow ended within a nested block of tasks.

This happened:

For the workflow that ended with a non-nested block, the .operation.executed.v1 event was successfully emitted. The orchestrator system listened to this event and marked the workflow as complete in the portal.

However, for the workflow that ended within a nested block, the .operation.executed.v1 event was not emitted. As a result, the orchestrator waited indefinitely for a response and was unable to mark the workflow call as complete.

I expected this:

A workflow completion event should be emitted for all workflows, regardless of whether they end inside or outside a nested block, and whether the outcome is success or failure.

Is there a workaround?

For workflows that end within a nested block, explicitly adding a final non-nested block at the end appears to ensure that the event is emitted properly.

Anything else?

No response

Platform(s)

Windows

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.name: Bug Report 🐞