Existing file system connections are not displayed

[fanweiyan-coder]

Describe the issue

#5398

Because this issue is closed, but the problem is not solved, so I have to submit this issue again. For details, you can also refer to the previous 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

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

Browser

Edge，Chrome

Additional context

No response

[rllyy97]

Hi @fanweiyan-coder, I'm a little confused on what behavior you're seeing from your explanation.
From my understanding you are adding an action, and creating a connection for it.
Then when you add another action of the same connector, the previously created connection is not appearing?
Is that correct?

[fanweiyan-coder]

Hi @rllyy97 Yes，your understanding is correct. Thank you for your support

[fanweiyan-coder]

Hi @rllyy97 Is there any progress? thank you.

[onyx-lemur]

@rllyy97 - any advice here as well? Experiencing the same issue - except sometimes File System connectors do not load at all (we have about 12 in our connections config and I prompted to make a new connection every time I create a new File System connector).

[rllyy97]

@onyx-lemur, I spoke with @fanweiyan-coder offline but it appeared that an older designer version was being used.
We released a new designer version a few weeks ago that should have a fix for this sort of issue.
Can you try taking a look at the designer version you are running on, and if it's not 2.41007.1.19 try clearing your cache and reloading to pick up the newest version. You can find steps to get your extension version from our docs here: https://agreeable-beach-04ed7ce1e.5.azurestaticapps.net/tsg#finding-your-session-id-or-portal-extension-version
If you are already running on the version I specified and still hitting the issue, can you take a har trace and email it to me at [email protected] for investigation? You can find steps for that process in our docs as well.

[onyx-lemur]

@rllyy97 - Can confirm that we're running on that latest version.

I will send you the HAR trace next time it pops up - however, we're doing UAT on some new WFs at the moment, so might take a while as we prioritise that.