IBM Security QRadar SOAR

Hello,

I am utilizing workers to run more expensive/lengthy actions in the background so that other actions can run. However, whenever I use them via self.fire, multiple instances of the function the worker is assigned to run occurs. For example, in my code the self.fire occurs only once and it is directed to run a function that eventually attaches a file to the incident. By pressing the button in resilient to cause the self.fire to occur and the function to run, the function is ran 5 times and the file is attached 5 times.

Is there some simple trick to avoid this multiplicity when using workers?

Please let me know if more details are needed as I understand this question is somewhat vague. 

Thank you,

Tyler Cole

------------------------------
Tyler Cole
------------------------------

Hi Tyler,

Could you provide sample code and/or simple diagram so we can get a better understanding of your environment?

------------------------------
JOHN PRENDERGAST
------------------------------

Original Message:
Sent: Tue March 03, 2020 12:10 PM
From: Tyler Cole
Subject: Workers causing multiple occurrences of the same event to fire

Hello,

I am utilizing workers to run more expensive/lengthy actions in the background so that other actions can run. However, whenever I use them via self.fire, multiple instances of the function the worker is assigned to run occurs. For example, in my code the self.fire occurs only once and it is directed to run a function that eventually attaches a file to the incident. By pressing the button in resilient to cause the self.fire to occur and the function to run, the function is ran 5 times and the file is attached 5 times.

Is there some simple trick to avoid this multiplicity when using workers?

Please let me know if more details are needed as I understand this question is somewhat vague. 

Thank you,

Tyler Cole

------------------------------
Tyler Cole
------------------------------

Hi John,

I appreciate it, but I decided to go another route for our purposes that does not require workers.

Thank!



------------------------------
Tyler Cole
------------------------------

Original Message:
Sent: Thu March 05, 2020 05:12 AM
From: JOHN PRENDERGAST
Subject: Workers causing multiple occurrences of the same event to fire

Hi Tyler,

Could you provide sample code and/or simple diagram so we can get a better understanding of your environment?

------------------------------
JOHN PRENDERGAST

Original Message:
Sent: Tue March 03, 2020 12:10 PM
From: Tyler Cole
Subject: Workers causing multiple occurrences of the same event to fire

Hello,

I am utilizing workers to run more expensive/lengthy actions in the background so that other actions can run. However, whenever I use them via self.fire, multiple instances of the function the worker is assigned to run occurs. For example, in my code the self.fire occurs only once and it is directed to run a function that eventually attaches a file to the incident. By pressing the button in resilient to cause the self.fire to occur and the function to run, the function is ran 5 times and the file is attached 5 times.

Is there some simple trick to avoid this multiplicity when using workers?

Please let me know if more details are needed as I understand this question is somewhat vague. 

Thank you,

Tyler Cole

------------------------------
Tyler Cole
------------------------------