We encountered a scenario where we were calling an AD spoke (Powershell) action when the associated MID server was down, and the flow failed with the MID server down issue.
Could you please suggest for retry policies for such cases.
Please follow the KB article steps. It would be HTTP.
Note: You can only create retry policies for JDBC, REST, and SOAP steps.
When using the retry policy, ensure that you are aware of these considerations:
Only a fixed time interval strategy is honoured for the data stream actions.
The total delay (count multiplied by the interval) can't exceed 30 seconds. For example, if you want retry for a maximum of 3 times, the maximum delay for each retry is 10 seconds.
Data stream step doesn’t go into the waiting state during retry.
Please Accept the solution if it assisted you with your question & Mark this response as Helpful. Regards Tanushree Maiti ServiceNow Technical Architect LinkedIn: https://www.linkedin.com/in/tanushreemaiti
