Android Mobile 3.21031.26 Client not triggering connected Power Automate Flow AT ALL

(0) Share

Report

Posted on by m3ngi3

725

I am experiencing the strangest issue ever with a Power Automate Flow connected to a Power App:

Power App uses SQL connector. SQL connector uses Power BI Gateway to connect to (very secured) managed instance of Azure SQL database (so not On-Prem, but same infra setup). Flow is directly triggered from button in Power App and has uses same SQL Connector to run stored procedure.

-Desktop App Player on all laptops will trigger the flow perfectly

-Native mobile client of multiple iOs devices will trigger the flow perfectly

-Native client of 2 Android phones we tested will NOT trigger flow... no errors... no notifications.... no flow run visible in Flow Studio (failed, canceled or otherwise)

-Browser App Player on same 2 Android phones will trigger the flow perfectly 🤯🤯🤯

Because of the premium connector we thought maybe license or account issues, but all users have premium per app licenses and my account even has a premium flow license. And even it was account related --> then how come it works on other devices for that same account...

I saw another topic where there was put a lot of focus of old (unused) connections in the Power App Definition (zip file) causing possible issues. You think an old reference to an old flow somewhere in the Power App could cause the flow not being triggered on only a specifc type of Native Mobile Client (version 3.21031.26) of Android???

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

RandyHayes 76,299 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Django

I am sensing a trend! This is at least the second post today with the same scenario.

I would suggest putting in a support request on this as it might be that something has gone wrong with the current player or PowerApp version.

I hope this is helpful for you.

Was this reply helpful? Yes No
m3ngi3 725 on at

Like (1)

Report
Copy link

Link copied!

Thanks @RandyHayes —> already a request pending 👍🏼

Will keep this post updated on the outcome 💪🏼

Was this reply helpful? Yes No
Verified answer

m3ngi3 725 on at

Like (1)

Report
Copy link

Link copied!

So an update from Microsoft: there were some changes on Microsoft side that could have caused this behavior.
Unfortunately, I was not able to wait until the fix so we removed the Flow from the Power App last week and created a different trigger to start an automated process instead of a Power-App-linked flow...

I will therefore close this discussion in the hope that Microsoft actually fixed it: if not --> log a ticket with Microsoft 👍

Was this reply helpful? Yes No