-
Notifications
You must be signed in to change notification settings - Fork 321
Description
Describe the Bug
We are experiencing unexpected behavior in an Azure Logic Apps Standard setup involving a stateful workflow calling a stateless workflow.
Scenario
We are using Azure Logic Apps Standard.
A stateful workflow invokes a stateless workflow.
In the stateless workflow, the debug mode is set to "Enabled on Failure".
Observed Behavior
In the Run History, the stateless workflow run is marked as Failed.
When inspecting the run details, only the successful actions are shown.
The execution simply stops after the last successful action.
No failed action is displayed.
No exception, error message, or termination reason is visible.
It appears as if the workflow execution just stops without reporting the underlying failure.
Expected Behavior
If a run is marked as Failed, we expect:
A visible failed action, OR
An error message, exception, or termination reason explaining the failure, OR
Any diagnostic information that clarifies why the run status is set to Failed.
Impact
This behavior makes troubleshooting difficult because there is no visible indication of what caused the failure.
Plan Type
Standard
Steps to Reproduce the Bug or Issue
- Create an Azure Logic Apps Standard instance.
- Create a Stateful workflow (Workflow A).
- Create a Stateless workflow (Workflow B).
- In Workflow B (stateless), enable Debug mode = "Enabled on Failure".
- In Workflow A (stateful), add an action that invokes Workflow B (e.g., using the built-in "Workflow" action).
- In Workflow B, configure a scenario that results in a failure (e.g., an HTTP action returning an error, or any action that can fail under certain conditions).
- Trigger Workflow A so that it calls Workflow B.
- Navigate to Run History of Workflow B.
Observe that:
The run status is marked as Failed.
Only successful actions are visible.
No failed action, error message, or termination reason is shown.
The execution appears to stop after the last successful action.
Workflow JSON
Screenshots or Videos
Additional context
No response