How to handle retry policy if a MID server is down when a flow action (AD/powershell) is executed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2026 07:58 PM - edited 05-05-2026 07:58 PM
Hi Team,
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.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2026 08:18 PM - edited 05-05-2026 08:18 PM
In your connection (http_connection.list table), instead of selecting specific MID server , you can select Auto-Select Mid Server . It will select a Running UP Mid server automatically.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2026 04:40 PM
Unfortunately we cannot do an auto-select MID server as the capabilities needed are not defined for all the MID servers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2026 08:22 PM
For Retry Policy , refer this KB: KB1638260 How to create a retry policy
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2026 04:42 PM
This does not help. Which connection type can I choose if a MID is down for any AD spoke action.