Adam

My feedback

  1. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Adam shared this idea  · 
  2. 608 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    29 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Adam commented  · 

    Stop creating infinite loops in flow.

    Sharepoint Designer excludes the triggered workflow when determining whether an item has been updated, ensuring the workflow won't recursively trigger itself in an infinite loop. In Flow there is no such consideration. So when I create a flow to fire every time a list item is changed, and the action is to update something in that list, the action of the flow triggers the flow again. Ergo, infinite loop.

    And stop telling the dev community how to work around it. We know how to work around it and create secondary columns that get flagged. The point is we should not have to come up with a workaround for such a stupid, unnecessary problem.

Feedback and Knowledge Base