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

[Ankur Bawiskar]

@AkkiYen 

share your playbook trigger condition and config screenshots

[AkkiYen]

Hi @Ankur Bawiskar,

Thanks for your response attached the Playbook trigger conditions.

Thanks

[Ankur Bawiskar]

@AkkiYen 

are you not using this in your playbook?

I am not seeing that

I am seeing this

[AkkiYen]

Sorry might have missed while pasting 

We are using record create or update here because, in our case, there are two ways a case can be created. Sometimes, the user updates the criteria of a case, so in that situation, I want to use it as a record create or update.