Hey @vanitharaj1208 ,

The best practice would be to implement the action with retry mechanism. Meaning that, if you've encountered status code 429, the action will wait until it will receive status code 200. In that way, over time the action will finish for all 10 alerts.

Retry mechanism will need to be done in async way. We have a lot of actions that work like that, you can look into action "Wait For Custom Fields" in Siemplify for inspiration.  

Hi @ylandovskyy ,

Can i get some info on modules which starts with TIPCommon and where can i find the code?

I have implemented with retry mechanism in sync action , its working but i'm not sure ... is this right way?

and  in this action "Wait For Custom Fields"  where is Retry mechanism is implemented i didn't find it?

@vanitharaj1208 

In terms of TIP Common, you can find the code base in the "Script Dependencies" section of the integration.

To review the code, you can export the integration itself and review the code locally in the "Dependencies" folder. If you wanted to include TIP common in your own integrations, Google had a post a few weeks ago on how to perform that action: https://www.googlecloudcommunity.com/gc/SecOps-SOAR/Retrieving-latest-version-of-TIPCommon-and-its-dependencies/m-p/891759#M3822 

hi @ylandovskyy , are you sure that we should go with async action ? 

It sounds best to me too.

There is a roadmap item for x retries, however that will be a little more limited in retry count compared to Async that can try for hours/days.