logicapps: In VSCode, Workflow Fails To Start after designer changes - Azurite 3.17.1 Extension

Scenario:

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)

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 1
Comments: 22

Most upvoted comments

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.

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.

HLChucky on May 5, 2022

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.

dancurtiss on May 4, 2022

We may resort to using actual azure storage until we can figure out how to get azurite to play nice with logic apps in VS code. I think this applies specifically to blob triggers as our other triggers continued to work locally I believe.

dancurtiss on Sep 7, 2022

Hi Everyone

I ran into this today as well - another workaround I have found is to use the full local development connection from the Azurite documentation in your local.settings.json file for the AzureWebJobsStorage setting - instead of UseDevelopmentStorage=true

I tested this using Azurite v3.18.0

Your local.settings.json should look this like

{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": "DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=http://127.0.0.1:10000/devstoreaccount1;QueueEndpoint=http://127.0.0.1:10001/devstoreaccount1;TableEndpoint=http://127.0.0.1:10002/devstoreaccount1;",
    "WORKFLOWS_SUBSCRIPTION_ID": "",
    "FUNCTIONS_WORKER_RUNTIME": "node"
  }
}

Documented here: https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azurite?tabs=visual-studio-code#https-connection-strings

Garyljackson on Jul 3, 2022