Need help in running Flow Designer flow

[nameisnani]

Hi Community,

Looking for guidance on cancelling a running Flow Designer flow via a Business Rule. Would really appreciate any help or pointers!

---

📌 BACKGROUND

We have a '3 Strike Rule' flow (Flow Designer) that triggers when an incident is placed On Hold with reason = Awaiting Caller. The flow sends strike notifications at scheduled intervals and auto-resolves the incident if there is no response.

---

❓ THE PROBLEM

If an agent updates the incident before the flow completes — either by changing the state away from On Hold, or by changing the hold reason from Awaiting Caller to something else (e.g. Awaiting Evidence or Awaiting Change) — the flow continues running and sends stale strike notifications even though the situation has already changed.

We want the flow to cancel automatically in two scenarios:

1. State changes from On Hold (Awaiting Caller) → any other state (In Progress, Resolved, etc.)
2. State stays On Hold but reason changes from Awaiting Caller → Awaiting Evidence or Awaiting Change

---

🙏 WHAT WE NEED HELP WITH

• Is a Business Rule the right approach to cancel a running Flow Designer flow, or is there a better way?
• Has anyone used sn_fd.FlowAPI.cancelFlowForRecord() for this — any gotchas to watch out for?
• Any advice on filter conditions or script logic to handle the two scenarios above cleanly?

---

We are on a recent ServiceNow release. Any guidance, examples, or links to docs would be hugely appreciated!

#FlowDesigner #BusinessRules #Incident #OnHold #Automation

[nameisnani]

@Siddhesh Jadhav  I am getting confused - could you please modify my script and could u please provide me the updated scrpt 

[nameisnani]

@Ankur Bawiskar  need your help - could you please help me here . please help in scritpt