Does an SPD OnChange Workflow prevent a Flow OnChange flow from triggering?

GDS_User01 41 Reputation points
2020-12-31T13:05:20.733+00:00

Am transitioning from SPD to Flow, but still have a legacy SPD 2013 WF triggering OnChange. This WF triggers as expected.

I cannot get the Flow OnChange flow to trigger, though, so trying to figure out why. Is SPD blocking Flow?

SharePoint
SharePoint
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
9,748 questions
SharePoint Workflow
SharePoint Workflow
SharePoint: A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.Workflow: An orchestrated and repeatable pattern of business activity, enabling data transformation, service provision, and information retrieval.
513 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Emily Du-MSFT 42,026 Reputation points Microsoft Vendor
    2021-01-01T09:12:29.627+00:00

    @GDS_User01
    Based on your description, I understand that your SharePoint Online both have workflows and flows to trigger changes. Workflows trigger changes as expected, but flows do not trigger changes. SharePoint designer will not block flows.

    Please check following tips.

    1.Check whether you create an automated flow to trigger changes.
    2.Check the flow run history to see if there are any errors.

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. GDS_User01 41 Reputation points
    2021-01-04T21:21:27.533+00:00

    I don't understand what you mean by "flows do not trigger changes". The have two triggers: Item Modified, and Item Modified or Created. But, I'll ignore that statement for now.

    It's good to know that SPD won't block flows, and it seems that SPD takes precedence over flows, meaning that SPD runs first, then flows come second. (I'm not 100%, though.)

    Other than that, I did select an "automated" trigger, but Flow does not fire it. (There are hundred of questions referring to this known issue, and it's completely aggravating that this is the case.) To overcome this, I had to use the "Item Created or Modified" automatic trigger instead.

    Finally, if the automatic trigger doesn't fire, then there nothing to see in the Run History.

    Please accept this response as the answer.