Hi Andrew,you may have some classic flows in Dynamics enabled that trigger off a field update done by the modern flow.
When, in turn, that update is completed, it might be the trigger for the modern flow to kick off again. You can try switching off all the classic and modern flows on the Opportunity entity and run this flow again. Let's see what that does.Can you post a screenshot of the trigger and the compose steps? I don't think it's in one of those, but we'll never know until we check.
Would you be comfortable posting a screenshot of your trigger and compose?
It may be that the filtering attributes or the filtering conditions are the culprit here, or maybe your compose loops somehow? A screenshot with your definitions will help.
Finally, could it be that the save option on your Dynamics record triggers workflows that, in their place, trigger the flow again?
If you've found this thread useful, dive deeper into User Group community content by role