Supabase Get Row Output Bug?

[sebauautu]

Hello,

I’m trying to do a quick filter on some of my items, so that I don’t process the duplicates.

Here is the quick summary of the flow:

1. Fetch some data from the api
2. Map the data as I need (array of items)
3. For each item in the array, try fetching from Supabase by the ID
4. Check if the item exists in Supabase or not and process the ones that do not exist
5. etc… not relevant

The problem:
I’m quite sure I’ve mapped the data correctly, while getting my items individually sent to the Supabase’s Get Row node. Get Row node is configured so it always returns an output regardless of the item existance. Get Row node returns 1 item instead of let’s say 50 (how many entered the node)

As as software dev myself, quite sure something is wrong with the node (or I have completely misunderstanding how it should work).

The flow:

50 items are clearly going into Get a Row.
Only 1 item is being dispatched (you should know that the Supabase table is fresh and will not have any matches in it). As I understood (talking to AI and reading the docs), Get a row should return an array of 50 empty objects. Then my If node should do it’s checks and continue.

What am I missing?

Thanks!

[sebauautu]

For anyone wondering, I’ve found a workaround.

I’ve added a Edit Fields node that just returns all the items from Split. Then I combine the two inputs and filter out the duplicates.

Works perfectly, although I’m still convinced the single empty object is not the correct output of Get a row from Supabase if I have multiple inputs