ECC queue retry policy

[chandra_ym]

Can I configure and make use of a "ECC Queue retry policy" to retry the failed/error'ed outgoing REST messages, even if i am not using a MID server for integration ?

I am integrating my ServiceNow instance with another ServiceNow instance by consuming it's REST end point. I would like to have retry mechanism in place to retry the failed REST message.

[Vikas-Malhotra]

Hi Chandra,

I would recommend using a do while loop using an async business rule to accomplish this. You can put the logic to try 5 times at max.

If you want to make it better, you can have a custom table to log all the failed cases in order to debug easily in future.

Please mark correct or helpful in case it helps.

Thanks!

Vikas

[chandra_ym]

hi Vicky, out of the box, ServiceNow provides ecc queue retry policy option to implement retry mechanism. I want to utilize this option instead of writing custom code to achieve this.

[Himanshu Dubey]

Hi chandra_ym,

Service now  provides OOB mechanism for ECC Queue retry policy you can use that.

Please mark correct and helpful if it helps in any way

Thanks & Regards

Himanshu Dubey 

[josh_nerius]

Hi Chandra, 

There are some good answers here. It's also worth noting that as of the New York release, there's a new Retry Policy feature in IntegrationHub. This allows you to define condition-based policies and choose from fixed interval or exponential backoff retry strategies. 

See https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/administer/flow-designer/concept... for more info. 

Note: These policies work with Flow Designer/IntegrationHub protocol steps, but not with legacy REST messages. 

-Josh