cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

PowerApps does not reliably trigger PowerAutomate Flows

Hi all,

 

I have a PowerApp as custom form for a SharePoint list. The SharePoint list has versioning enabled, so I have clear track when users updated list items via the PowerApp.

 

In the PowerApp, the OnSuceess property of the SharePointForm1 is triggering a PowerAutomate Flow.

Now I recognized that PowerApps does not reliably trigger PowerAutomate Flows. This morning a user made two item updates via the PowerApp and no PowerAutomate Flow was triggered.

 

Has someone experienced the same issue and can recommend how to deal with that, please?

 

Frankly spoken, I recently observe "trigger is not executing Flow" issues with different trigger, e. g. "SharePoint list item created or modified". So looks like PowerApps and PowerAutomate are not ready for real production business applications.

12 REPLIES 12
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @heldry ,

This may not be a solution, more an assurance that this is not normal behavior.

We trigger thousands of Flows monthly both directly from PowerApps and from "when an item is created or changed". One of the latter synchronizes a customer list with up to a hundred entries daily and we have never found a discrepancy.

Many of the PowerApps triggered ones store photos in Libraries and have done over 30,000 reliably.

Maybe there is an issue with the trigger.

 

Hi WarrenBelz,

 

Thanks for your feedback.

 

I have already a ticket open with Microsoft and they confirmed that "SharePoint list item is created or changed" on lists with versioning enabled does not reliably trigger flows. They claim that this is a SharePoint  issue and there are no plans fix this.

 

They advised to trigger the Flow from PowerApps and today I found that this is not reliable either. I have updated the ticket with my findings and I'm waiting for response.

 

Not sure if these issues are related to the load in MS's data centers these days.

Do you have some monitoring in place that helps to detect if Flows are not executed? I have a SharePoint Designer workflow that executes on item created or modified and then logs the item ID, version, modified date and modified by to a SharePoint list. That allows to check the Flow log and to detected these issues.

 

WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @heldry ,

We also have versioning enabled on the list, but not the photo library as they are never changed after filing.

The synchronizing is only to show the customer what is going on and is on a sub-site for security reasons. We are actually looking to change this to a Patch in PowerApps to reduce Flow run totals.

We have not got any monitoring with the volume involved - we would have to manually check thousands of entries in case one sync item did not work. As many fields can be changed on any record during a day, the next Flow would fix it.

Thank you anyway for bringing this to the attention of the Forum - it is useful to know.

v-xida-msft
Community Support
Community Support

Hi @heldry ,

Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned. The flow fires successfully when I made a change using PowerApps custom form in my SP List (which has enabled "Version History" option).

4.JPG

 

Please check if you have specified proper Site Address and List Name within the "When an item is created or modified" trigger.

 

The "When an item is created or modified" trigger of SharePoint connector may take almost 1 minute to fire after you made changes in your SP List, it would not be fired immediately after you made changes to your SP List.

Also please check if you have created a connection to the "When an item is created or modified" trigger using your own proper credential.

 

If the issue still exists, I think PowerApps trigger button could achieve your needs. You could consider use "PowerApps" button as Trigger of your flow, then within the following actions, specify these parameters you want to pass from your app using "Ask in PowerApps" dynamic content of PowerApps trigger.

Configure your flow as above screenshotConfigure your flow as above screenshotNote: Configure your flow as above screenshot. 

Within your custom form app, set the OnSuccess property of SharePointForm1 to following:

'Flow Name'.Run(Argument1, Argument2, ....); // Add formula here to fire flow from your custom form app
ResetForm(SharePointForm1);
RequestHide()

Note: Please provide proper value for these arguments of your 'Flow Name'.Run(...) function. These arguments represents these parameters defined in your flow using "Ask in PowerApps" dynamic content

 

More details about firing a flow from an app, please check the following article or video resource:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/using-logic-flows

https://www.youtube.com/watch?v=1wl9AtxWdkg
 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi Kris,

 

thanks for your feeback and for looking into this.

 

The instructions you provided are helpful if Flows never trigger and the user has to configure and get it working the first time. But that is not the case in my situation. I have worked a lot with triggers and Flows in the last days and in principle that works.

 

However it does not work reliable!

 

For SP lists with versioning enabaled MS support already confirmed to me that there is an issue with the "list item created or modified" trigger. They did not provide much details except there are no plan to fix this.

 

For PowerApps triggering PowerAutomate Flow, I counted this morning 110 triggers and 2 of them did not execute a Flow. Versioning proves that the list item was updated, I confirmed with the user that it was done via the PowerApp, but the Flow was not executed. I also raised this in my ticket with MS, but have no helpful response so far.

 

If a trigger does not relably execute a Flow, then Flow is not usable for business applications.

Hi @heldry 

 

I have observed similar issue where Flow is triggered in OnSuccess event. In 99% cases it works, but sometimes we just see that form has been submitted (in version history) but Flow is never triggered. 

Maybe if moving to button triggered it would resolve this? But then it would have to wait for the actual submit to finish as it relies on the data in SharePoint item. Does anyone have any suggestions for this?

 

Just for reference, here is what we are doing in OnSuccess:

If(SharePointForm.LastSubmit.Status = "STATUS VALUE", 'FlowName'.Run("STATUS VALUE", "", SharePointForm1.LastSubmit.ID, First(Filter(collContacts,TeamName="Some team name")).EMail, ""));

// code removed for brevity

ResetForm(SharePointForm);
NewForm(SharePointForm);

I thought it has something to do with this First(Filter... clause, but checked with populating label in app and it's always filled in with data. Collection is created on OnNew or OnEdit events in SharePoint Integration. 

Generally I face a lot of issues with Flows being triggered from Power Apps, apart from this one which leads me to conclusion that it shouldn't be ever used as doesn't work reliably. I though of changing this to react on SharePoint events rather than events in app itself, but as I understand @heldry  you have experienced issues with that as well?

 

Hi @mpil ,

 

initially I used "SP list item created or modified" as trigger for the Flow, but that was not reliably executing the Flow each time the trigger occurred. We opened a ticket with MS and they said it's a known limitation when versioning is enabled on the list and they have no plans to fix this. Disabling versioning is not a option for me.

 

So MS recommended to trigger the Flow directly from the PowerApp (same as you're doing) but I found again triggers that did not execute the Flow. I have one critical application which I am monitoring closely and there I experience 1.7% of the triggers not resulting in a Flow being executed ... an operational nightmare. There is not really progress on resolving this issue, so I had to look for alternatives.

 

For my critical application I am now using this setup: A small and simple SharePoint Designer workflow is "SP list item created or modified" and adds an item with id and version to a list that functions as queue of changes to be processed. A PowerShell script is pulling the queue every few minutes, is performing the workflow actions and cleaning the queue items when done. This is pretty robust and reliable.

 

So summing up my experience:

  • Triggering the Flow with "SP list item created or modified" does not work reliable if versioning is enabled on the list and there is no plan to fix this
  • Triggering the Flow with "SP list item created or modified" may work reliable if versioning is disabled on the list. I have not tested this myself.
  • Triggering the Flow directly from the PowerApp does not work reliable (~1.7% triggers don't execute the Flow). MS is investigating and may fix this one day.
  • Using the workaround with SPD workflow and PowerShell script pretty robust and reliable.


Hope this helps

 

Thanks @heldry for info - it's really useful, will keep these in mind. 

I have actually been able to find the root cause of the problem by adding additional screen with loading animation and confirmation message that processing is done, which is set on OnSuccess after running the Flow. For most users all of this works perfectly well, but we have couple of users that actually got a toast message with error 'Flow.Run failed: The method 'Run' has invalid value for parameter 'param'' - it seems they must have been getting this error earlier, but since the form was being closed automatically with RequestHide(), they couldn't really see it. 
Flow is expecting string value, but for some reason it probably got null (or BLANK, as I think PowerApps don't really use nulls). The funny part is that these values are always populated in OnEdit or OnNew events, so they must have been reset somehow. Additionally, for these users sometimes this whole process works perfectly and sometimes they got this error, so I don't really get it. 

Maybe your case is similar?

PaulD1
Community Champion
Community Champion

Just a thought, but have you tried using Logic Apps instead of Flow? I believe they use the same connector so it probably does not make a difference, but might be worth a try.

Could you be hitting the API rate limit?

I'd be very wary of using SharePoint lists, Flows and PowerApps for critical business processes.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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 in the Forums 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**   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. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     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. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (3,201)