Powerapp: triggering of powerautomate not in Run History

[CedricOsei]

Context: 
I am managing a Powerapp, which is used internally by different stakeholders to book events. Due to the need of various internal stakeholder having access everyone within the AD is authorised to the application as user.

General Description of issue: 
Unfortunately the application doesn't seem to trigger the underlying powerautomates, completely within during some of the calls by users. In order to mitigate this phenomenon and find a clearer more sustainable solution - other than deleting and adding the flows again - I wanted to audit the runhistory of the powerautomate of the powerapp, to see where things went wrong. Unfortunately these calls are not visible in the flows run history, hence making debugging and pathing nearly impossible. 

Has anyone faced similar problems or has a solution to further debug and patch the problem? 

Sidenote: 
The application is managed within a solution. And the solutions updates is then always migrated from DEV to PROD environment.

 

[Geeks_D]

If the runs are not in history the Flow is not triggered from the app 

[CedricOsei]

@Geeks_D 
but how would it be able to execute the first part of the flow and note a specific slot as booked?

[Geeks_D]

This is a bit tricky to answer 
I will need to see the code that is meant to trigger the flow from PowerApps 

[CedricOsei]

[Geeks_D]

Okay I can see that a trigger is sent to the flow with 2 variable
The flow should run OnSelect of this 
Can you remove the flow from app and re-add again to try this 
Plus run a test on the flow from Power Automate as well 
Also check you Appcheck for all error reporting 

[CedricOsei]

Thats the thing, It works seamlessly even without removing the powerautomate for most users - with run history and everything. But from time to time it just doesn't execute the entire flow nor appear in the run history...

And removing and adding the flow unfortunately did not solve the problem permanently or give the run history persistently 

[Geeks_D]

Hmm I think this is coming from the Environments  are you  looking history in the right environment  

[CedricOsei]

Yes, made sure to double check the effect and flow on both environments.
When trigged in PROD and the flow in PROD has the run history if it is not one of the cases with the issue. And the DEV environment shows no effect from triggers in prod in any way.

Could renaming the flows on the respective PROD environment help?