web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Power Apps Trigger Doe...
Power Automate
Suggested Answer

Power Apps Trigger Does Not Run The Flow

(0) ShareShare
ReportReport
Posted on by 12
I have a code in Power Apps that runs a set of actions, refer below code snippet.
        //PART 1 - WRITE PV FORM
        PRDWritePVForm.Run(
            //SOME INPUT PARAMETERS HERE
        );
        //PART 2 - ASSIGN TO NONE
        Patch(
            //SOME PATCHING TO SHAREPOINT LIST HERE
        );
        UpdateContext({loadingText: "Sending Notifications"}); //UPDATE LOADING SCREEN VALUE
        UpdateContext({loadValue: 3});
        //PART 3 - NOTIFY SSC
        IfError(
            PRDNotifySSC.Run(
                //SOME INPUT PARAMETERS HERE
            ),
            Patch(
                //SHAREPOINT LIST,
                Defaults(//SHAREPOINT LIST),
                {
                    Message: FirstError.Message,
                    Source: FirstError.Source
                }
            )
        );
        //PART 4 - NOTIFY REQUESTOR
        PRDNotifyRequestor.Run(
            //SOME INPUT PARAMETERS HERE
        )
 
This code is run after the approval of a request.
The code running well on PART 1 - 4, most of the time. However, PART 3 randomly does not run (or the trigger fails) over time.
The function is to run a Power Automate flow. The flow will send an email, containing information of a request.
The function is also wrapped in an IfError() function, to track if the flow call failed.
 
For example, refer to screen snip below.
PRDWritePVForm > Run history
 
PRDNotifyRequestor > Run history
 
 
In this example, there are 4 approvals happening in a short time range: Request ID 2363, 2368, 2367, 2365.
All three flows are running for Request ID 2363, 2368, and 2367.
However, PRDNotifySSC does not run for Request ID 2365.
 
Additionally, the PRDNotifySSC call is wrapped with IfError() function. But there is no error recorded.
 
Any insight for this issue helps a lot.
Thanks in advance!
Categories:
I have the same question (0)
  • Mark Nanneman Profile Picture
    991 Super User 2025 Season 2 on at
    Before you put an IfError() arround the PRDNotifySSC run would it show runtime errors inside PowerApps?
     
    Did you try running the app with the live monitor session to debug?
  • WiranataLim Profile Picture
    12 on at
     
    Thanks for your reply.
    The app ran by end users, and I have not received any feedback regarding errors.
    Therefore, I put an IfError() around the flow call to make sure the errors are recorded.
     
    I haven't tried running the app in monitored session. Perhaps I will try this.
     
    Appreciate it!
  • Mark Nanneman Profile Picture
    991 Super User 2025 Season 2 on at
    My guess would be there's some issue with the payload in your PRDNotifySSC.Run().  There might be cases in which the data passed is missing or doesn't match the Power Automate Power Apps trigger schema and it can't trigger.

    I'd recommend doing some QA testing using the live monitor and see what changes cause errors with that flow.

    You can also try removing and re-adding the flow to the power app, and republish.
  • Suggested answer
    WiranataLim Profile Picture
    12 on at
    Update:
     
    I look again into the issue and find a possible cause.
     
    The trigger of PRDNotifySSC is set with concurrency control of 1, to have the triggers run in queue for some requirement.
    In a very specific scenario, there are rapid approvals within a tight time range, causing queue to build up.
    I checked that apparently waiting runs are limited to 10 queues only. Any other triggers beyond the queue limit are not processed (and without any indication). This cause triggers that do not result in flow runs, causing confusion upon troubleshooting.

    I have re-created PRDNotifySSC with concurrency control set to off and do some adjustments to meet the requirement.
    For now, it has been working fine. Still, I will observe it closely.
  • WiranataLim Profile Picture
    12 on at
     
    Thank you very much for your recommendation.
    I did QA testing with live monitor and able to find more insights of the app, even that are not related to this issue, and still improved the experience of using the app.
     
    To update, I have some findings that could be the root cause of the issue and managed to fix it.
    I explained it in the suggested answer.
     
    It would be great if you could check it out, and more insights would be greatly appreciated.
    Thanks!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 525 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 324 Moderator

#3
abm abm Profile Picture

abm abm 232 Most Valuable Professional

Last 30 days Overall leaderboard