In VSCode, Workflow Fails To Start after designer changes - Azurite 3.17.1 Extension
See original GitHub issueScenario:
- Logic App workflow starts and runs correctly
- Make any updates to logic app workflow which would require a rebuild of the logic app
- Attempt to run logic app again
2022-04-29T14:28:28.932Z] Workflow Error: operationName='WorkflowDefinitionProvider.ProcessWorkflow', message='Workflow 'xxx' validate and create workflow
failed, the error is 'Unexpected HTTP status code '412'.'', exception='Microsoft.WindowsAzure.Storage.StorageException: Unexpected HTTP status code '412'.
[2022-04-29T14:28:28.936Z] at Microsoft.WindowsAzure.ResourceStack.Common.Storage.Http.Parsers.FastCloudTableParser.UpdateEntitiesFromResponse(TableBatchOperation batch, MemoryStream content, RequestResult operationResult)
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:22
Top Results From Across the Web
workflow designer not starting in vscode
When I click on Open Designer context menu for workflow.json it fails to start designer and the output is below.
Read more >VS Code has suddenly stopped displaying Logic App ...
After reading your post, I checked my Azurite extension as well, just in case. And it turns out, it too was updated yesterday....
Read more >Azurite
Extension supports following Visual Studio Code commands: Azurite: Start Start all Azurite services; Azurite: Close Close all Azurite services; Azurite: Clean ...
Read more >Developing Logic App Standard Workflow Using Visual Studio ...
Open visual studio code and go to Extension and search for Azurite and install it (as highlighted below). Add Azurite extension in Visual ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For me the issue was the new Azurite extension version - downgrading to v3.16 resolved the issue. I’ve kept the Azure Logic Apps Standard extension at v1.0.19 and don’t have any issues. Thanks for the tip 😃
One thing to add is that I had to delete the existing Azurite files (blobstorage, azurite_db_blob.json etc.) that had been created and reload VSCode to get rid of the error.
Thank you for the input. It does seem to be due to VSCode extension updates to Azure Logic App Designer and maybe more importantly Azurite.
I’ve downgraded these to:
Azure Logic Apps (standard) v1.0.14 Azurite v3.16
Seems to be working again now. I’ll leave this open to get notified when fixed.