OOB Restricting Playbook re-triggering on open cases

[AkkiYen]

Hi Team,

I am currently using the "Once / Only if not currently running" run type for our Playbooks. However, I’ve noticed that if an existing Playbook is marked as Complete or Skipped while the Case remains open, subsequent updates to the Case trigger a new Playbook instance.
Is there an Out-of-the-Box (OOB) configuration to strictly limit Playbook execution to once per record lifecycle, regardless of the previous instance's completion status?

Thanks,
AkkiYen

[AkkiYen · Accepted solution]

We found that the field was causing the issue, and when unchecked, it solved our issue.