Parameters for 'Number of Retry' and 'Time Delay' in some transformers when fail

Agreed! For now the only solution I can think of is to create a Custom Transformer with HTTPCaller and a Loop (Counter, Tester) for implementing resubmit attempts.

With cloud services we often run into either gateway timeouts or rate limits when doing batch operations. It would be incredible if there was a Python code editor in the HTTPCaller that was invoked on <Rejected>, where you could write Python code to inspect headers etc. and tell the HTTPCaller to either retry in a number of seconds, or to reject the connection. This proposition is based on the fact that rate limits exists in so many different flavors, that I'm suspecting it's not feasible to support them all out of the box (see https://tools.ietf.org/id/draft-polli-ratelimit-headers-00.html).

@david_r​ Have you seen this addition to HTTPCaller (FME 2021.2 and 2022.0)? It sounds like this might be able to work with the scenario you had started to describe above. (I'd be happy to pass on or highlight any feedback you have about this!)

Amazing, how did I miss that one... Thank you, Rylan! Now I just need to convince our users to upgrade :-)

I just did a bit of testing due to a client experiencing server-side timeouts (Http status 524). Unfortunately this particular error doesn't seem to be supported. It's not a choice in the list of 5xx error codes, and it also doesn't seem to be included in the "Connection Errors" category. I ran it against https://httpstat.us/524 with a backoff time of three seconds, but it failed straightaway.

It'd be brilliant if the transformer allowed us to use custom error codes. There are some APIs out there that respond in weird and wonderful ways when things go wrong.

@Jan Roggisch​ Agree completely

Yes I need this with a the wfs-reader (in the featurereader!)