cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JPMontoya
Helper II
Helper II

flaky connector for shared flow

Hi,

 

I have run into an issue with a flaky connector in a shared flow.

A bit of context: there are four components in play, 3 flows & 1 powerapp, which acts as a control-center of sort. In the app, data is entered by the user and the flows are run with that data. The 3 flows run sequentially (f1, f2, then f3), with each of them providing input for the subsequent flow. In Testing this whole construct for myself, I never experienced any kind of issue like this, the behaviour of the connector-actions was always consistent.

Now, to do a pilot-run of the whole thing, I shared both the 3 flows, as well as the PowerApp with a second user in our environment. Now the situation is as follows: If I run the whole thing, it uses my credentials to perform all the actions, it gets the files from my oneDrive, etc. When she runs it, it uses her credentials, uses her files etc. (as it should be).

However, in all of her runs, the action 'list rows present in a table' of the excel online for business connector is misbehaving. In the first flow it gets called with dynamically set inputs for Location, Document Library ID, FileID & TableID. The action works as expected and lists all the rows. This is done mostly to verify the dynamic inputs early.

In the third flow, the exact same action is used with the exact same inputs, but there she gets a 404.

works.png

does not work.png

As I mentioned, none of this happens when I run the flow. The Inputs are correct, I manually verified all of the IDs that are being used. I simply can't imagine what might cause such a behaviour.

The only thing that comes to mind is that for the third flow in her runs the excel connector somehow tries to access files on my oneDrive with IDs that have been identified (and verified in f1) on her oneDrive, so basically the connection not using her credentials but mine instead. I don't know however where I can check for such information and am quite generally at a loss as to what to do.

 

Any help, ideas or resources is very welcome

 

cheers,

JP

1 ACCEPTED SOLUTION

Accepted Solutions

Hi Ricardo (@rimatos)

 

Thanks for responding and sorry for the late reaction on my part, hectic times.

 

Regarding the sequencing. No I am not using Child Flows. I am using context-variables to store the responses from the previous flows. in that response there is a property that tracks whether the flow is successful, and only once that property equals 'true', the next flow will be launched. So e.g. the command for f2 to run looks like this:

If(_f1_response.success = "true", UpdateContext({_f2_response: f2.Run(...)}))

 

I have sort of figured out what caused the problem but I am not sure how to interpret my findings. Let me give some context:

In my post here I described an issue where my flow f3 (the one acting up with the excel-connector) always got triggered 4 times when the chain of flows was initiated from my PowerApp.

To fix this I attempted all the suggested fixes like duplicating the flow, removing and readding the flow to the PowerApp etc. but nothing worked. The final thing I tried was the 'Concurrency Control' for the trigger of the flow. This fixed the issue with the flow triggering multiple times.

However, it seems to me that the 'Concurrency Control' somehow messes with Connections in shared flows and causes the problem I described in the initial post in this thread. I duplicated my flow f3 and nuked basically everything except the one action that caused problems. Still, the issue remained. I then tried turning off the 'Concurrency Control' again, which is not possible. I then was able to reproduce the Connection issue (working for me, not working for whoever I share the flow with) in a different Tenant with a number of simple flows (consisting each only of a single action that uses a connection) by turning on 'Concurrency Control'. So this is not limited to just the Excel-Connector.

I then, rather annoyed I might add, spent a couple of hours recreating the troublesome flow from scratch without 'Concurrency Control' on the trigger, not running into either my initial issue with the multiple-runs getting triggered, nor this issue with connections not working when shared.

 

So ultimately it looks to me that my "fix" for the initial issue caused this particular problem. I can't however say that I'm entirely satisfied with this result as I don't understand

  • why exactly concurrency control on the triggers causes such a connection issue with Teamflows
  • why the initial problem with the quadruple-runs happened in the first place.

and I would quite like to avoid this happening to future flows of mine.

 

So in a way this topic can be closed I guess, since I quite frankly neither have the knowledge nor the time to investigate this any further. Still, if this is a known problem or the cause for the quadruple-runs is clear, then I'd obviously love to know to avoid future problems.

 

best regards,

JP

View solution in original post

5 REPLIES 5
JPMontoya
Helper II
Helper II

Ok, I have done some experimenting with this on a tenant where I have access to multiple accounts. It seems that for whatever reason, when sharing the third flow, the connections don't switch over automatically from the "sharer's" connection to the connections of the person who received the flow (as can be seen in the screenshot, it doesn't use "my connections" from the point of view of the recipient of a shared flow).

 

Screenshot 2020-08-24 at 13.15.22.png

This obviously is not exactly brilliant, as now all new recipients need to manually switch over all of their connections, which means that they either have to be guided through this or be given extensive instructions, as there are a lot of actions in this flow that use connections.

This is also not exclusive to Excel, as it turns out. It was just the first to be used and thus fail. All connections including Custom Connectors need to have their connections swapped.

If I had to make a guess I would say that this is either due to the size / complexity of the flow or alternatively due to the fact that the concurrency control of the trigger is set to 1 for this particular flow (seems less likely to me).

 

Therefore I have to wonder if anyone else has had a similar thing happen and if that is a known & expected behaviour.

 

cheers,

JP

JPMontoya
Helper II
Helper II

Update: scratch my second comment. First off, none of the other shared flows switch connections over to the ones of the recipient and they still work. Second off, actually switching the connections manually only breaks things further.

rimatos
Community Support
Community Support

Hi @JPMontoya ,

 

How are you ensuring that the Flows are being called in sequentially? Is it using Child Flows?

 

Additionally, would it be possible to show a screenshot of how you are inserting the data in the list rows action in the 3rd Flow which is misbehaving?

 

Regards,

Ricardo

Hi Ricardo (@rimatos)

 

Thanks for responding and sorry for the late reaction on my part, hectic times.

 

Regarding the sequencing. No I am not using Child Flows. I am using context-variables to store the responses from the previous flows. in that response there is a property that tracks whether the flow is successful, and only once that property equals 'true', the next flow will be launched. So e.g. the command for f2 to run looks like this:

If(_f1_response.success = "true", UpdateContext({_f2_response: f2.Run(...)}))

 

I have sort of figured out what caused the problem but I am not sure how to interpret my findings. Let me give some context:

In my post here I described an issue where my flow f3 (the one acting up with the excel-connector) always got triggered 4 times when the chain of flows was initiated from my PowerApp.

To fix this I attempted all the suggested fixes like duplicating the flow, removing and readding the flow to the PowerApp etc. but nothing worked. The final thing I tried was the 'Concurrency Control' for the trigger of the flow. This fixed the issue with the flow triggering multiple times.

However, it seems to me that the 'Concurrency Control' somehow messes with Connections in shared flows and causes the problem I described in the initial post in this thread. I duplicated my flow f3 and nuked basically everything except the one action that caused problems. Still, the issue remained. I then tried turning off the 'Concurrency Control' again, which is not possible. I then was able to reproduce the Connection issue (working for me, not working for whoever I share the flow with) in a different Tenant with a number of simple flows (consisting each only of a single action that uses a connection) by turning on 'Concurrency Control'. So this is not limited to just the Excel-Connector.

I then, rather annoyed I might add, spent a couple of hours recreating the troublesome flow from scratch without 'Concurrency Control' on the trigger, not running into either my initial issue with the multiple-runs getting triggered, nor this issue with connections not working when shared.

 

So ultimately it looks to me that my "fix" for the initial issue caused this particular problem. I can't however say that I'm entirely satisfied with this result as I don't understand

  • why exactly concurrency control on the triggers causes such a connection issue with Teamflows
  • why the initial problem with the quadruple-runs happened in the first place.

and I would quite like to avoid this happening to future flows of mine.

 

So in a way this topic can be closed I guess, since I quite frankly neither have the knowledge nor the time to investigate this any further. Still, if this is a known problem or the cause for the quadruple-runs is clear, then I'd obviously love to know to avoid future problems.

 

best regards,

JP

Thank you for the reply on this @JPMontoya , it was very informative.

The best i can advise as of now would be if you face any of these mentioned issues in your Flow to raise a Support ticket through https://admin.powerplatform.microsoft.com/support, so we can troubleshoot this in more detail and understand what can be causing the issue.

Unless we have a working repro of the issue and/or an error message to continue it is a sensitive issue to troubleshoot.

 

Hope this helps!

Regards,

Ricardo 

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders   UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery:  https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   Week 2 Results:  Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏 Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Top Kudoed Authors
Users online (4,120)