Action Retries

scenario alex works in a security operations center (soc) she is responsible for discovering and reporting malicious urls she receives a report of urls each morning she looks up each of the urls, and then uses the resulting scans to report which urls are most severe this takes up most of alex's morning each work day alex wants to use turbine to simplify and automate this process she has already ensured that her version of turbine has downloaded and configured the urlscan connector from swimlane content and created/saved a scan urls playbook, and reviewed the report to determine which data she wants to use to feed her swimlane application(s) and playbook alex can resolve this scenario with the following solution build an application that includes data fields and a playbook button that serves as a record action trigger alex created the scanning urls application with the following data fields url , date & time , and description , and added the playbook button to link her scan urls playbook that she already created with the application complete, alex can return to the scan urls playbook to configure her data the playbook trigger is the record action (via the application playbook button) add the submit connector that will submit urls for analysis alex is ready to configure the connector by adding the urlscan asset, which she preconfigured with the needed url and api key data click the plus icon for select from available assets and add urlscan alex promotes the result in outputs now, she is ready to get the results click on success action flow and add the get results connector alex is ready to configure the action retry parameters this ensures the action retries until the parameter criteria is met click configure for the get result connector, and then set up the parameters under retry you will see default seconds and retry attempts; however, you will need to set the conditions alex clicks manage conditions and creates the first condition by selecting status code from the available playbook properties then, sets the status code to 200 and clicks apply next, enter the desired seconds and retry attempts that you want alex applies the parameters and returns to the playbook she confirms the retry is set by seeing the retry icon around the action to verify the playbook, action, and retry parameters are correct, she tests the playbook conclusion alex now starts her day knowing that she has automated searching and reporting malicious urls