Closed jdefesche1 closed 3 months ago
@rllyy97 can you take a look?
Hi @jdefesche1, if you recreated another workflow with the same code view, I would guess it might be something related to how you have your connections defined. Could you send your connections json to me at rileyevans@microsoft.com and I'll take a look? Feel free to obfuscate anything that might be sensitive, but leave any parameter references in place please, I think those could be causing this
Hi @rllyy97,
I sent you the code. Meanwhile I have been investigating myself as well. I think I found the problem. In our arm template we have a variable called sqlConnectionManagedApiId
"sqlConnectionManagedApiId": "[concat('/subscriptions/', subscription().subscriptionId, '/providers/Microsoft.Web/locations/', parameters('location'), '/managedApis/sql')]",
We use this variable to point to the correct api id. For our troubling logic apps I noticed that the first slash in front of subscriptions was missing. After adding that, the problem went away.
@jdefesche1 Glad you were able to get it fixed! I'm going to close the issue but if you have anything else to add feel free to comment again and we can reopen if needed
Describe the Bug with repro steps
With the new Logic App designer any action using an ApiConnection is showing an error 'Unable to initialize operation'
What type of Logic App Is this happening in?
Consumption (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Screenshots or Videos
Browser
Firefox
Additional context
If I create a similar logic app by hand in the portal it works (no errors), but I can't find any relevant differences in the code views.