Flow Designer record trigger (Created or Updated) causes duplicate email on insert - best practice?

[鳴鏑張]

Hi everyone,

I’m building a notification flow on table “x_xxxxxxxxx”.

Goal:
- Send 1 email to multiple recipients when status becomes “xxxx” (re-review pending)
- Cover both create and update scenarios

Current implementation:
- Record trigger: “Created or Updated”
- Recipient list is built with Flow Variables (collect IDs in loop, convert to email list outside loop)
- Send Email step is outside the loop (single send)

Issue:
When a new knowledge record is inserted, the flow seems to run twice (create + immediate update), so duplicate email can be sent.

Questions:
1. Is this expected behavior for “Created or Updated” triggers?
2. Is it better practice to split into two flows?
- Flow A: Created + status = “xxxx”
- Flow B: Updated + status changes to “xxxx”
3. If keeping one flow, what is the recommended guard condition to avoid duplicates?

I’d appreciate any recommended pattern from production experience.
Thanks in advance.

[brianlan25]

Is the record ever inserted with status of xxxx? If so then I would do a conditions state changes to xxxx otherwise the flow will trigger on update no even if the state did not change but something else did as the state is xxxx.