Steps that make use of API Connections show "Unable to initialize operation"

[las3r]

Describe the Bug with repro steps

I have a couple of steps in my logic app that are using API Connections (Microsoft.Web/connections):

1. Keyvault connection (get secret)

2. Event grid connection (trigger for logic apps)

In the old designer these would load, and I would be able to change the steps. In the new designer every step that utilizes an API connection shows the following:

Event hub trigger:

Keyvault "get secret" step:

The request I see it making a few calls when the page loads to:

GET https://management.azure.com/subscriptions/<subscription>/providers/Microsoft.Web/locations/westeurope/apiOperations?%24top=5000&%24skiptoken=10000&%24filter=type%20eq%20%27Microsoft.Web%2flocations%2fmanagedApis%2fapiOperations%27%20and%20properties%2fintegrationServiceEnvironmentResourceId%20eq%20null&api-version=2018-07-01-preview

The response to this call is:

{ 
value: []
}

What type of Logic App Is this happening in?

Consumption (Portal)

Which operating system are you using?

Windows

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

{
  "When_a_CustomerCaseUpdate_event_occurs": {
    "splitOn": "@triggerBody()",
    "splitOnConfiguration": {
      "correlation": {
        "clientTrackingId": "@coalesce(triggerBody()?['id'], guid())"
      }
    },

    "type": "ApiConnectionWebhook",
    "inputs": {
      "body": {
        "properties": {
          "destination": {
            "endpointType": "webhook",
            "properties": {
              "endpointUrl": "@{listCallbackUrl()}"
            }
          },
          "filter": {
            "includedEventTypes": [
              "CustomerCase"
            ]
          },
          "topic": "@concat(parameters('subscriptionId'), '/resourceGroups/', parameters('infra').environment.resourceGroup, '/providers/Microsoft.EventGrid/domains/', parameters('infra').eventGrid.name)"
        }
      },
      "host": {
        "connection": {
          "name": "@parameters('$connections')['azureeventgrid']['connectionId']"
        }
      },
      "path": "@concat(parameters('subscriptionId'), '/providers/Microsoft.EventGrid.Domains/resource/eventSubscriptions')",
      "queries": {
        "x-ms-api-version": "2017-09-15-preview"
      }
    }
  }
}

Screenshots or Videos

No response

Browser

Edge, Chrome

Additional context

• There are no 500's in the network tab
• There are no console errors.
• This worked fine in the old designer/

[rllyy97]

Hi @las3r, thank you for reporting this issue, we have received a few reports of this issue and have created a parent ticket here that you can use to track progress: #5977

[ccastrotrejo]

Hi @las3r I wasn't able to repro it yet.

• Is there any chance we can get your workflow json schema from your logic app? It seems that the one posted above its just from the trigger. You can share it with me to my email [email protected]

Usually this error "message": "Unable to initialize operation details for swagger based operation - When_a_CustomerCaseCommentUpdate_event_occurs. Error details - Operation Id cannot be determined from definition and swagger", gets thrown when there isn't a match between the action id and the actions we get from the connector swagger.

[las3r]

• workflow json schema from your logic app? It seems that the one posted above its just from the trigger. You can share i

You've got mail!

[ccastrotrejo]

Thanks I just received it. Will let you know if I need something else or if I find anything going on

[ccastrotrejo]

@las3r Just replied back via email.

[las3r]

I have just replied to @ccastrotrejo. Seems the new designer doesn't really like the way we provide the "path" parameter to API connection-based logic app actions. We're getting closer!

[ccastrotrejo]

Hi @las3r I replied to your email, could you please try the scenarios I stated on the email. Thanks!

[ccastrotrejo]

Hi @las3r as discussed on the email thread, the way you are parameterizing the path in the action is not ideal. I tested it in old designer and doesn't seem to work either. Could you please give it a try in the old designer and confirm it works with this private url?
https://aka.ms/lafallback

[github-actions]

We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed.

[github-actions]

This issue has been closed because the information requested wasn't provided within 7 days.