HTTP Request Node "Retry on Fail" feature

Hello n8n experts,

I recently realised that if the “HTTP Request” fails to process one item (and the retry toggle is enable) it will retry all input items instead of just the one that failed.

Is this intended? It doesn’t make much sense, does it?

Workflow to reproduce the bug:

When running the above workflow we can see in the console how all input items are being reprocessed.

Information on our n8n setup

  • n8n version: 1.63.1
  • Database (default: SQLite): postgresql 14.8
  • n8n EXECUTIONS_PROCESS setting (default: own, main): queue
  • Running n8n via (Docker, npm, n8n cloud, desktop app): kubernetes
  • Operating system: Amazon Linux EKS 1.28.5-20240227
2 Likes

Hey @Fortian , thanks for reporting. I think you are right and do not think that this is the right behaviour. We will investigate it further.

1 Like

@ihortom do we know when we can get the fix for this?

1 Like

Hey @avi , the issue is still being reviewed and we do not have the set time to have it resolved yet. However, it has been acknowledge as a bug.

Hello @ihortom,

Any news about this bug?

We just realised that if we have the “Continue (using error output)” enabled and “Max. Tries” equal to 3, if the first attempt fails it will run all the 3 attempts even if the second one success! This is a big source of issues!

On top of it, even if the second (and third!) try success it’s providing an item in the “Error” output which is nonsense.

The “Continue (using error output)” and the “Retry On Fail” are two important features that should be reliable!

When are we going to get a proper fix?

P.S.: Part of the above was reported back in September "Retry On Fail" does not work as expected if "On Error" is set to "Continue" · Issue #10763 · n8n-io/n8n · GitHub!

2 Likes

It is still in backlog. Might take quite a while for the engineering team to place hands on it. Sorry.

This is currently marked as “Closed - Not Planned”

I was hoping it would get some attention since the UI allows you to set it up with this invalid combination of things.

I keep forgetting it doesn’t work and trying it again. Wish the UI would at least keep you from doing it. Seems like it should be possible to configure the UI such that if "Retry on Fail" is enabled, "On Error" disappears and defaults to "Stop Workflow"

1 Like

its not important

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.