Baserow Retry on Fail are executing every time

[tiago-mdr]

Bug Description

I haven't been able to reproduce this manually but it is happening in multiple scenarios, I had baserow retry on Fail set to 5 and 5000 ms, and I kept getting 5 repeated entries 5 seconds apart.

I also noticed all other Baserow nodes (including get all and update), were taking >25000ms , they are actually being ran 5 times.

I tried replicating this with manual execution but I haven't been able to. I will post again if I'm able to do so.

Running self-hosted n8n Version 1.85.4, Baserow Node Version 1.

To Reproduce

Haven't been able to yet.

Expected behavior

No double entries should happen on success.

Operating System

unsure

n8n Version

1.85.4

Node.js Version

idk

Database

PostgreSQL

Execution mode

main (default)

[Joffcom]

Hey @tiago-mdr,

We have created an internal ticket to look into this which we will be tracking as "GHC-1470"

[tiago-mdr]

I've been able to reproduce it with a simple "GetAll" node, it happens even without any filters, ordering etc.

I'm using selfhosted baserow, last version, 1.32

With Max Tries 5, 5000ms

Without Retry it returns in less than 1000ms.

While not 100% sure, I think this was already happening for quite some time, I remember having duplicate entries for quite some time. It just became noticeable because I had some issues with my baserow instance and started adding the retry to all nodes.

[Joffcom]

Hey @tiago-mdr

This is something we are aware of, it is a general issue with the retry we have on all nodes. Rather than ignore the successful events we send them again which can cause duplication.

A possible workaround is to manually build out the retry using the on error use output branch option then adding in another insert or update event.

[tiago-mdr]

Hello @Joffcom

So is this something that is happening with all nodes? I don't see other people reporting this issue.

The retry feature is not critical in most of our workflows so for now so I'll avoid the workaround. But would be nice to know when I can safely get back to using the retry feature 🙂

[Joffcom]

Hey @tiago-mdr,

yeah it is an issue with all nodes when using the retry, We were going to look at fixing it last quarter but didn't get a chance to but it is on the future list.

For now I am going to close this and I will link it to the internal ticket so that when we do fix this you can be notified.