Hi, I am trying to implement a simple HTTP call with retry on failure. The failure could be a network issue that generates an "exception" or a service failure, where the HTTP call returns a failure code (say, not 200) and it is not an exception. In both cases I need to retry the HTTP call. I tried…

Thank you. Adding a rate limit node does help avoid multiple triggers. The only challenge is to find the right time to rate limit it to. When the service returns an error code (say 500), it does so under 1 second and so, the retry does not work. I can find a time interval that would work for both an…

[image] kartikn: Adding a rate limit node does help avoid multiple triggers. The only challenge is to find the right time to rate limit it to That can be solved with an additional 1sec delay from the function retry output and another from the catch node (both delays feed into the rate limit). …

Handling retry on failure from HTTP nodes

General

Steve-Mcl 8 September 2020 17:50 2

One option would be to put a rate limit node set to 1 msg per second immediately before the http node.

Note, it isn't really a good idea to have the catch node retry the operation it catches as you could potentially cause a loop that crashes node red.

Topic		Replies	Views
Duplicate message on http error? General docker	19	193	4 December 2025
DNS retry on HTTP Request node General http-request	3	219	21 March 2023
[ANNOUNCE] @waldbaer/node-red-retry Share Your Nodes	8	274	10 October 2024
Flow for Integration With a Secure WebApi Endpoint General	12	158	10 December 2025
HTTP Request exception handilng problem General	3	1150	6 April 2021

Handling retry on failure from HTTP nodes

Related topics