This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 31%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
I have deployed my standard logic app workflow using azure DevOps
when i try to edit it from portal it gives following error
@priyansh Thank you for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.
Based on the error message, we understand that you are trying to update the logic app workflow from the portal, and this might be failed due to invalid syntax.
Could you please help us more information what you are trying to do.
I would suggest you do F12 traces to see the exact error message and also about the ajaxextended failed call.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 21%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPD%3C/text%3E%3C/svg%3E)
Hi can you please elaborate how F12 traces can perform
@priyansh Thanks for your response, F12 traces are nothing but network traces that can be captured in a web browser's developer tools. They provide a detailed record of all the network requests made by a web page, including information about the request and response headers, the request and response bodies, and the timing of each request. This information can be very useful for troubleshooting network-related issues with web applications.
Refer to this documentation for more information on how to capture F12 network traces from different browsers.
@priyansh Just following up to see if you have any chance to check my previous response and helped. Do let me know if you have any further questions on this.
<<Removing the traces>> Here is the F12 traces files
hey @VenkateshDodda-MSFT can you please look at those F12 log file
@priyansh Thanks for sharing the information, We have looked at the shared log file and we see that the operation Save workflow is failed with the error Unauthorized Access exception because of this you are ended up with Ajax Call failed error in the portal as expected.
I would suggest you check with admin and get the respective permission to create\update the workflow in the standard logic app.
Feel free to reach back to me if you have any further questions on this.
@VenkateshDodda-MSFT I tired with the owner role but it didn't work. can you please mention which permission I need to create/update the workflow in the standard logic app.
@priyansh Thanks for your response, Just want to check do you have the owner permission at the subscription level or at the logic app or resource group level ?
@VenkateshDodda-MSFT i have owner permission at subscription level
@priyansh This would need one on one offline support, for deeper investigations and might need to engage product team as well.
I will suggest you open a support ticket. In case if you don't have the support plan then please send an email with your SubscriptionID and link to this thread to AzCommunity@microsoft.com with subject line as "ATTN: Venkatesh" so I can enable one-time free support on your subscription to assist you further.
sure i will do it
@VenkateshDodda-MSFT Thank you for the free support. I got the solution. We need to remove WEBSITE_RUN_FROM_PACKAGE from the app setting and when we are deploying through DevOps, we need to choose zip deployment as the deployment method.
@Priyansh Desai Thanks for sharing the solution for the benefit of community, glad to know your problem has been resolved.