Forum Discussion
Solved
Auto Generate Incremental ID
Hello... I have just joined this community to seek some assistance. (Sorry I am not able to upload images for reason, so I apologize in advance for the wordy message). I am having problems wi...
APZee - This behavior is unfortunately by design and working as expected per Microsoft. See here: https://learn.microsoft.com/en-us/power-automate/disable-flow. What we've recommended to users is before turning the flow back on, add a terminate step right after the trigger. This will still run the flow, but quickly clear the queued events. Best of luck!
APZee - This behavior is unfortunately by design and working as expected per Microsoft. See here: https://learn.microsoft.com/en-us/power-automate/disable-flow. What we've recommended to users is before turning the flow back on, add a terminate step right after the trigger. This will still run the flow, but quickly clear the queued events. Best of luck!
- Thank you for the feedback. I can confirm I had the same information provided by our MS Partner also. The workaround or solution I have implemented to avoid this is to add one additional column in the list, "DataImported" with a default value set as No (For new items being created) and set the previously uploaded data as DataImported=Yes. Then simply added a condition to Terminate any item that is flagged as DataImported=Yes. So, the workflow is only really running when new items are added, and the existing data is skipped.
