logicapps icon indicating copy to clipboard operation
logicapps copied to clipboard

Cannot edit LA standard workflows in Portal that were originally developed in VS Code

Open daverobinson64 opened this issue 2 years ago • 2 comments

Apologies if this is raised elsewhere but I cannot find anything.

If I develop a Logic App standard workflow in VS Code when I deploy to Azure and attempt to edit in the portal it will not let me save it and I get the following error

Failed to save workflow ajaxExtended call failed

From what I've seen in the documentation I should be able to edit it, but have I missed something here?

Point 4 of the following links suggests you should be able to

  • https://docs.microsoft.com/en-us/azure/logic-apps/create-single-tenant-workflows-visual-studio-code#manage-deployed-logic-apps-in-the-portal

daverobinson64 avatar Apr 23 '22 10:04 daverobinson64

I am facing the same issue here. with LogicApp standard (west-europe). In the past I was able to edit the LogicApp workfl;ow that was originally deployed with Azure DevOps (zip deployment). Now it is not possible anymore, with the exception message described in the topic start. What was changed that introduced this (unwanted, unexpected(?)) behaviour? Thanks in advance!

rob-thijssen avatar May 10 '22 10:05 rob-thijssen

@daverobinson64, I found out what was wrong with our LogicApps at our side. Due to a change in our deployment pipelines, the WEBSITE_RUN_FROM_PACKAGE was set to 1. This caused the behaviour that we couldn't edit the logicApp workflows in the portal. After fixing the pipeline back to the original settings, the WEBSITE_RUN_FROM_PACKAGE now is deleted again before deployment. Maybe this setting is also present at your configuration settings? Set it to 0, or delete it, and you will be able to edit the LogicApps in the portal again.

rob-thijssen avatar Jun 13 '22 20:06 rob-thijssen

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] avatar Oct 20 '22 21:10 github-actions[bot]

This issue was closed because it has been inactive for 7 days since being marked as stale.

github-actions[bot] avatar Oct 27 '22 22:10 github-actions[bot]