LogicApps Custom connector - Unable to initialize operation details for swagger operation

[fsarabia]

Describe the Bug with repro steps

After the UX migration to the new designer, a workflow that uses a custom connector stopped working.

The custom connector action finishes as successful (green check) even though it shows the message "Unable to initialize operation details for swagger based operation - Error details - Incomplete information for operation ''" during the run history. I'm also unable to edit the operation and the tabs "Parameters, Settings, Code View, Testing, About" do not appear.

This custom connector uses a "dynamic" connection.
"connection": {
"name": "@parameters('$connections') [variables('dynamicConnName')]['connectionId']"
}

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

No response

Screenshots or Videos

No response

Browser

Chrome

Additional context

No response

[harshalCG]

Having the same exact issue as above, any leads will be helpful thanks

[rllyy97]

Hi @fsarabia + @harshalCG,

I'm currently investigating this issue, could either/both of you send me your workflow.json file?
Possibly also your connections.json file just to be safe, feel free to remove anything values might think are sensitive if you'd like
My email is [email protected]

[preetriti1]

We are unable to resolve the connections because it refers logic app variables in combination with workflow parameters. Currently this is an unsupported scenario because variable values are determined or changed during runtime. We do not resolve variables in the connection expression but we do for workflow parameters.
If this is an arm template variable then this should be sent as resolved before we load the designer, but looks like it is LA variables.

[fsarabia]

The flow is not failing, it executes as it should but it shows the error/warning in the runtime log which is very confusing. It’s understandable that it cannot resolve a dynamic connection, but this warning is misleading and it didn’t work like that before. Thanks!

…

On Mon, Apr 29, 2024 at 7:21 PM preetriti1 ***@***.***> wrote: We are unable to resolve the connections because it refers logic app variables in combination with workflow parameters. Currently this is an unsupported scenario because variable values are determined or changed during runtime. We do not resolve variables in the connection expression but we do for workflow parameters. If this is an arm template variable then this should be sent as resolved before we load the designer, but looks like it is LA variables. — Reply to this email directly, view it on GitHub <#4675 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGALEMLVDCF5TLT5GTCTPVTY73533AVCNFSM6AAAAABGT32VO2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBUGIYDKMZVHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[preetriti1]

@fsarabia PLease send a screenshot of which warning you are talking about.

[fsarabia]

See the screenshots, I also have included one from the previous UX for you to compare. Thanks! All images are from run history. [image: Screenshot 2024-04-30 at 2.54.02 PM.png] [image: Screenshot 2024-04-30 at 2.54.14 PM.png] Previous UX (no warning/error displayed) [image: Screenshot 2024-04-30 at 2.55.09 PM.png]

…

On Tue, Apr 30, 2024 at 1:14 PM preetriti1 ***@***.***> wrote: @fsarabia <https://github.com/fsarabia> PLease send a screenshot of which warning you are talking about. — Reply to this email directly, view it on GitHub <#4675 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGALEMMVUEF3OVZ3GYAR5CDY773SVAVCNFSM6AAAAABGT32VO2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBXGA2TEMBRG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[preetriti1]

@fsarabia - I do not see any screenshots attached. Can you please reattach the screenshots?

[harshalCG]

I was able to get past this error, had to switch from the new designer view to the old designer view and that solved the issue