Good afternoon! Our team has a flow that generates a notification email when a Sharepoint record is created. We needed to migrate some records over from our previous list and temporarily turned off the flow to avoid sending out a bunch of emails. A couple days later we turned the flow back on, and then it went ahead and processed all of those "new" records and sent out the emails anyway.
Is there another way for us to be able to temporarily suspend the flow activity to prevent this from happening? Is there a reason why even though the flow was turned off that when it was turned on it still ran for each of those copied records?
Thanks for your insight!
Solved! Go to Solution.
You can add Control Action Terminate after When an item is created in SharePoint and save it. Now your team can work on migration. The flow will trigger but will not generate a notification email and will stop. Once migration is done. You can remove the Control Action Terminate and save the flow. Please refer below sample flow:
Please accept the solution if this help you.
Regards
Kaif
You can add Control Action Terminate after When an item is created in SharePoint and save it. Now your team can work on migration. The flow will trigger but will not generate a notification email and will stop. Once migration is done. You can remove the Control Action Terminate and save the flow. Please refer below sample flow:
Please accept the solution if this help you.
Regards
Kaif
Thank you! I wish I knew why it still ran afterward, but at least we have something we can do to work around it. I'll share the info with my team.
User | Count |
---|---|
6 | |
6 | |
4 | |
4 | |
2 |
User | Count |
---|---|
8 | |
8 | |
4 | |
4 | |
4 |