Hi @v-liwei-msft
The flow acts as a way to detect creations and modifications as well as updating items on the list.
Due to current limitations we can only have one flow per form. I will explain each process:
When an item is created the flow needs to assign a unique ID number done through initialising a variable, the flow also grabs attachments when an item is created by " get attachments ", then initialising am array variable, followed by get properties then attaching the variable to the email. The final step of the created flow is updating the Unique ID column with update item.
To stop the infinite loop the first condition is to check if the unique ID column has been updated, and if it has (by adding in the unique ID) the flow has no next step.
For modifying it only needs to recognise status changes which is a reason for the third condition. This then sends an email and stops the flow.
I was just wondering if there is any work around for the attachment issue and as the moment everything else is working fine. Thanks
