HTTPOutbound Retry / Reprocess for REST and SOAP outside of ECC Queue

[Chan Soler]

Hi,

We would like to reach out and seek guidance on implementing a process within ServiceNow to be able to retry/reprocess HTTPOutbound failures under a range of response status code. This retry/reprocess would check first the response status codes of the HTTPOutbounds and will then wait for a certain number of seconds/minutes to attempt and retry/reprocess the transaction. We would like to know if this can be done outside of the ECC Queue Retry policy as currently some of the existing messages are sent using the execute method and not executeAsync therefore it does not reside in the ECC Queue. Has there been any solution for this kind of situation? Thanks!

[josh_nerius]

Hello, 

In the New York release, we added a new Retry Policy feature for IntegrationHub. This allows you to check against multiple attributes of the HTTP response to decide whether or not to retry the request. This supports Fixed Interval and Exponential Backoff retry strategies to give you control over the duration of time to wait between retries. 

This is unrelated to the ECC Queue feature. 

-Josh

[stuartgriffiths]

Hi Josh.

Background to my post is we are developing an outbound integration using async REST message calls which we are sending to the ECC queue. I'm looking at error handling options and was expecting the retry policy to form part that.

You state the new Retry Policy feature in New York is not related to the ECC Queue (Retry Policy) feature. I note that the last mention of the ECC Queue feature is in the London release docs. Also when I search for the ECC Queue Retry Policy plugin in HI it's not showing up.

Q. Does that imply the ECC Queue Retry Policy plugin is now redundant ie the new feature replaces it?

Q. Is the ECC Queue Retry Policy plugin still available?

Also I'm running some tests using the Integration Hub Retry Policy and have thus far failed to get my test policy to 'fire'. I've created a test policy with some basic conditions (screen shot below) and am creating an outbound REST request via a background script (the script ensures the endpoint URL is invalid hence triggering the 404 response). I've tried this both async and synchronous and so far I can see no evidence of retry attempts in the Outbound HTTP Logs.

Note: We do not have an Integration Hub subscription but the application and the Retry Policy module are available via the navigator menu.

Q. Is there a step I'm missing that would enable the Retry Policy?

Thanks in advance for any guidance.

Stuart.

[stuartgriffiths]

As I was under time pressure I raised a query on HI. Response below in case this is useful.

-----------------------------------

I would like to confirm the following is correct for the issue you are currently facing:

Issue: Outbound REST Integration: retry policy question

Business Impact: Medium

Investigation Summary:

-- We could see the plugins are still available in New York and Orlando releases. You may need to a raise a Hi case for plugin activation. Please refer the KB: KB0787200

-- The Retry policy which you have created if for Integration hub. This will work only in REST/SOAP steps in integration hub Please refer the Doc: https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/administer/flow-designer/concept...