Open nobuko-yamada opened 5 days ago
It isn't efficient.
For example, we can deploy the code unexpectedly like below including terminate action within ForEach.
Only after the opening from AzurePortal, we can find the validation error of the code.
Standard (VSCode)
Windows
New Designer
Yes
{ "definition": { "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#", "actions": { "For_each": { "type": "Foreach", "foreach": "@range(0,3)", "actions": { "Terminate": { "type": "Terminate", "inputs": { "runStatus": "Failed", "runError": { "code": "9", "message": "error" } } } }, "runAfter": {} } }, "triggers": { "When_a_HTTP_request_is_received": { "type": "Request", "kind": "Http" } }, "contentVersion": "1.0.0.0", "outputs": {}, "parameters": {} }, "kind": "Stateful" }
No response
via VSCode.
We can refer: Do not allow to save if there are illegal steps on a workflow. · Issue #984 · Azure/logicapps (github.com)
Describe the Bug with repro steps
It isn't efficient.
For example, we can deploy the code unexpectedly like below including terminate action within ForEach.
Only after the opening from AzurePortal, we can find the validation error of the code.
What type of Logic App Is this happening in?
Standard (VSCode)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Screenshots or Videos
No response
Browser
via VSCode.
Additional context
No response