Reruning playbook and preventing communication tasks from being rerun

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Reruning playbook and preventing communication tasks from being rerun

L3 Networker

Hello All,

I have been working on the XSOAR Platform for a long time and there is something which I haven't been able to find a solution for. 

I would like to rerun a playbook for multiple incidents and I use the !setPlaybook to do this. I do this after rectifying the issue on the playbook for example task error or similar. The problem is that many playbooks we are working with have a communication task such as Ask User or a Slack notification. 

Is there a way to rerun the playbook and prevent the communication tasks from running? 

As you can understand this can be an issue especially if the incident is not so recent therefore the communication task would be superfluous. I understand that you can re-run a stopped-on error task yet this can cause the same problem because it will reach the communication stage. 

I would be interested to know if there is a way to tag or cause the communications tasks to skip only during this rerun. 

Many thanks.

Cortex XSOAR 

1 accepted solution

Accepted Solutions

L4 Transporter

One way I can think of is have the communication task set a value into Context using the Set automation.

 

Then add a conditional in front of your DC tasks that checks whether that Key is set, and bypass the task if so.  

 

On the first run it will work, on the following runs it will skip them.

View solution in original post

2 REPLIES 2

L4 Transporter

One way I can think of is have the communication task set a value into Context using the Set automation.

 

Then add a conditional in front of your DC tasks that checks whether that Key is set, and bypass the task if so.  

 

On the first run it will work, on the following runs it will skip them.

@MBeauchamp2 , Thanks for the insight. It is possible that I can add this flow for all playbooks no matter how laborious it is. It is a shame that there is not way to manage communication tasks from an overview level. I could look into a feature request. 

I will mark your answer as a solution even though it is more of a workaround. 

Cheers. 

 

  • 1 accepted solution
  • 1545 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!