Closed andreyza-tr closed 2 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-logicapps-team.
Author: | andreyza-tr |
---|---|
Assignees: | - |
Labels: | `question`, `customer-reported`, `Logic App`, `Service Attention`, `needs-triage` |
Milestone: | - |
route to service team
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-logicapps-team.
Author: | andreyza-tr |
---|---|
Assignees: | - |
Labels: | `Service Attention`, `Logic App`, `customer-reported` |
Milestone: | - |
route to service team
The fix is available in logic 0.1.5 (latest version), and you can upgrade extension to latest version using command “az extension update –name logic” to try the fix.
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az logic workflow show Extension Name: logic. Version: 0.1.4.
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az logic workflow show --resource-group {} --name {}
Expected Behavior
Environment Summary
Additional Context