cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Flows appearing in incorrect document libraries/list

Hey all,

 

This seems to be a fairly recent issue that I was hoping would be hotfixed but still seems to be here after the weekend. I own several manually triggered flows that have begun appearing in the flow dropdowns for any list/document library they interact with with the update file properties or update item actions.  For example, the "Restore File" flow shown below is manually triggered in a separate library than where this dropdown exists. 

image.png

 

This same unexpected behaviour can be found in lists as well, with the "Approve & Distribute" flow shown above appearing in a list it updates an item for. 

I have only tested currently with the update actions but I am hesistant to think the same wouldn't occur if I was creating an item in these lists or libraries. Any help on preventing these flows from showing up would be appreciated, as we are currently exploring converting our various update actions to SharePoint HTTP Requests, but this would be cumbersome to maintain.

 

 

 

4 REPLIES 4
v-yamao-msft
Community Support
Community Support

Hi @Anonymous,

 

Could you share screenshots on your flow configuration?

Are there flows with the trigger For a selected item?

Do you mean that flows that are triggered by For a selected item don’t appear properly under correct lists or libraries?

In another word, flow “Restore File” should be under the library1, but it is now under Library2?

I have made flows for testing based on both lists and libraries. The issue you mentioned cannot be reproduced by me.

Please share more details to help reproduce.

 

Best regards,

Mabel

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

Hi @v-yamao-msft,

 

Below is my configuration for one of the problem flows, SOI LAP - Restore File:

 

image.png

 

The For a selected item is defined for the Deletion Library, with the Update moved file properties - Restored acting in the SOI Document Library, and Update Master List item acting in Master List

 


Do you mean that flows that are triggered by For a selected item don’t appear properly under correct lists or libraries?

In another word, flow “Restore File” should be under the library1, but it is now under Library2?

 


Not quite. This flow appears under Deletion Library and SOI Document Library and Master List. I have confirmed on my side that it is the update actions that are causing the flow to appear in the incorrect places. Below are screenshots of the flow appearing in the different locations.

 

image.png
image.png

  image.png

 

I get the same issue and have spoken to MS support. It appears in every Library which your flow has a connection too. This should absolutley be treated as a bug, as it allows you start the incorrect flow - which obviously instantly fails. Very confusing for the users

I have the same problem. I want to use a flow to send an item to another lists and it appears in both list instead of just one. Please fix it 

Helpful resources

Announcements
MPA_User Group Leader_768x460.jpg

Manage your user group events

Check out the News & Announcements to learn more.

V3_PVA CAmpaign Carousel.png

Community Challenge - Giveaways!

Participate in the Power Virtual Agents Community Challenge

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

PowerPlatform 768x460.png

Microsoft Learn

Check out our new Discover Your Career Path blog post series and get all the details.

Top Solution Authors
Users online (1,142)