You’re offline. This is a read only version of the page.
Announcements
73
We're building a service on Power Apps Portal and Power Automate.
Users will submit forms form the portal and a flow will be triggered by the Dataverse trigger 'When a row is created, updated or deleted'.
Our flow works just as we want, correctly.
But some triggered seemed skipped time to time, which made a crucial problem to our business operation.
We examined the cases and have found that only triggers made from Portal twice without interval were skipped.
And always the second attempts were ignored.
Not appeared on the run history either.
In short, if a user makes submit action twice on the Portal, the second submission is not going to trigger the flow.
When we observed how much interval is needed to make sure the two submissions result in two runs, just waiting to make sure the first run is completed was enough.
Could anyone give us some applicable knowledge please?
We have some workaround in mind but it takes a lot of workload... so, if anyone knows the very cause of this unwelcome event, we'd like to get rid of or make a small customize to avoid it.
The flow trigger is set to 'Created, Updated and Deleted', which is kind of required.
But we might have a second thought of removing 'Create' to prevent serial submissions from triggering the flow.
We also confirmed the trigger condition is correctly set.
Share
Report
All responses (
Answers (
