Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Unanswered

Synchronous PA Flow on HTTP Trigger with Disassociate Webhook

(0) ShareShare
ReportReport
Posted on by

Hello everyone,

I have the following situation:

This flow is designed to delete or add datasets when two datasets connected via association are disassociated.
The PA Flow Trigger is HTTP Request (concurrency limited to =1) and the web-hook step trigger is set on "disassociate".

The order in which the requests are processed matter, thus the flow-runs have to be synchronous.
My flow covers all possible combinations on how these specific datasets are disassociated.

For example: I trigger one disassociation between a table contacts and the table salesorders by removing the contact from the salesorder.
Depending on certain contact field values different delete or add actions should happen.

If Contact A with attribute A is removed and then Contact B with attribute B, something different should happen than if Contact A with attribute B is removed and then Contact B with attribute A.
Each flow needs an up to date image of the dataset.
If the flow allows parallelism it could for example try to delete something that isn't there or add something that shouldn't be. That's why they can't be asynchronous. 

If I wait after each HTTP-Request for the flow to complete (I trigger the flow by removing one contact from the salesorder), the correct results show.
I tested all possible combinations that matter multiple times, so it doesn't matter in which order the requests are processed.

But, if I trigger all HTTP-Requests one after the other, without waiting for the each to complete, it throws errors.

Specifically: The first request arrived triggers the flow and successfully completes it,
but the following requests triggering the flow result in errors, because these flows somehow have a different image of the dataset used to trigger it.

This happens, even though the scheduler shows that the other flow-runs are "Waiting" for the first flow to finish.

Found "solutions":

Researching about the problem I found similar stories. One suggested to use a response to force waiting for the flow completion.
But this is not possible for operators such as "associate" or "disassociate".

Does anyone have a similar experience and possible solutions?
I am grateful for any response.

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

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Daivat Vartak (v-9davar) Profile Picture

Daivat Vartak (v-9d... 181 Super User 2025 Season 1

#2
Siv Sagar Profile Picture

Siv Sagar 149 Super User 2025 Season 1

#3
Vahid Ghafarpour Profile Picture

Vahid Ghafarpour 124 Super User 2025 Season 1

Product updates

Dynamics 365 release plans