search

Azure / LogicAppsUX

https://learn.microsoft.com/azure/logic-apps
MIT License
74 stars 80 forks source link

Existing file system connections are not displayed #5398

Closed fanweiyan-coder closed 2 days ago

fanweiyan-coder commented 4 weeks ago

Describe the issue

  1. go to a standard logic app
  2. click the designer under the stateful workflow
  3. add an action, and select create file of the file system (on promise)
  4. The connection that I created before is not displayed, and I need to enter the information again

  5. After about five to ten minutes, the previous connection can be selected

    Note：He had established more than 20 file system connections.

Are you using new designer or old designer

New Designer (With action panels)

Screenshots or Videos

The first image is the problem status page. The second image is the normal page after waiting five to 10 minutes

1723685942788

1723686094005

Browser

Edge，Chrome

Additional context

Not sure if it is the same problem, the file system connector（on promise） sometimes shows an error as shown below, but we did not click many times

1723686289992

hartra344 commented 3 weeks ago

I'm not sure this is a UX bug, could be a API bug. Can you please open an ICM ticket on the Logic Apps team to investigate? Please include HAR traces and console log errors where appropriate.

fanweiyan-coder commented 1 week ago

Hi @hartra344 , we created a icm ticket before，but received as follows ： "in Logic App, when we try to retrieve the API connection of a specific connector, it is an API call send to ARM API (Resource Groups - List - REST API (Azure Resource Management) | Microsoft Learn).

By default, it has a limitation that how many resources can be returned in a single call if it cannot be retrieved for the first time, it will provide "nextLink" in http response for the next integration which I saw in cx's HAR trace.

Meanwhile, as per my understanding, the filter is applied after we retrieve the list, so it possible that we have an empty list but with "nextLink", so this issue mostly due to too many API connections in cx's resource group, but I believe we should consider this situation and fix in front end."

Could you have a look? Thanks. request： a2210947c25271393c8cd3b32676857

response： 3a059ced1255ef8f8096ff0a2e2690a

hartra344 commented 2 days ago

Should be fixed in #5595 . Fix will make it to production over the next couple of weeks.