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.

[Tony Chatfield1]

Hi, I use the ecc retry policy /queue successfully without a mid server and have no issues to-date, other than it not having oob mechanism to update the payloads auth token (when this is the cause of failure). As auth based retries are not common I added a simple BR that updates the failed payloads if required.

[chandra_ym]

Hi Tony, thanks for the reply. Based on your experience with outbound REST integration, what are the common retry scenarios which needed retry policy?

[Tony Chatfield1]

Hi, I would think that connectivity and target server response would be the 2 main issues seen but with service-now to service-now integration (hosted) you would normally only encounter these scenarios during upgrade/patching or instance data centre cut over and both these activities are scheduled and notified in advance. Auth issues should only be during a very small window, ie if you have an integration message trigger while the token is being updated.

[ash1xh]

Could you please share some details on how you created the BR?