Skip to Content
Technical Articles
Author's profile photo Mintu Chirayil Philipose

New Retry Feature for HTTP Receiver Adapter


With the introduction of the ‘retry’ inbuilt feature to the HTTP receiver adapter in the recent release, we can explicitly set the flow to retry the network connection based on the received response code. This is being achieved by polling for the defined retry count at a defined time interval.


This feature targets to overcome the following:

  • Operational load on a system, example any temporary server unavailability for short duration like server overload, will no longer cause the flow to go into an error state.
  • No more hassle to restart the flow manually.

Customer Scenario:

Imagine a salesperson approaches a potential lead. On visit gets the details of the business or the organization from the merchant, who requested for point-of-sale equipment.

And then process’s the details into his mobile app and submits the contract.

Meanwhile, the salesperson now need not await the server confirmation and can proceed to the next lead visit.

Sample Flow Design Logic

Sample Design


At the HTTP Receiver Adapter end,

  • The feature is only available when the checkbox is checked (by default)
  • Check the checkbox
  • And then one can specify, for what all different kind of response code the Inbuilt Retry should be done in the below field.

(One can mention code between 400-599, but any special character not supported like * or 5*)

  • Retry Interval can be set within the defined range of 5-60 sec.


  • Max Retry Iterations can only be defined 1-3, to avoid reaching retry rate limit.




The Flow can be monitored in below following ways.

  • The open text view log explicitly defines the number of retries tried.
  • For every Retry triggered the header of request and response and the response body is captured as attachments for reference


  • One can also monitor the retry tried in Debug /Trace Mode by HTTP Reattempt Counter


This feature would be helpful to overcome intermittent network connection to server and would help to manage message processing failures.

Please do share your thoughts and feedback over comments.

Also, would love to know other use cases, where you feel this feature could be used.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Sai Pachipulusu
      Sai Pachipulusu

      Nice Blog Mintu,

      From which integration version this feature is available ? currently not available for our version 6.46.5

      Author's profile photo Mintu Chirayil Philipose
      Mintu Chirayil Philipose
      Blog Post Author

      Hi Sai

      Thanks for your comment


      This feature is available as part of software version 7.18.* in NEO and in CF should be available in 6.46.* for runtime 8.10.*

      You can verify the runtime under About section.

      Note*: Currently Cloud Integration software rollout for both CF and Neo is being done in a phased manner and started for some Data Centers.
      As of now, there is a delay in rolling out to pending Data Centers due to unforeseen circumstances.
      Hence, we are unable to provide tentative timeline for this matter. As soon as the challenges are overcome, we will update you with potential dates.
      We appreciate your understanding and patience in this regard.

      Author's profile photo Guilherme Lahr
      Guilherme Lahr

      Thanks Mintu.
      Nice feature!