Baserow node with strange behaviour

[Noro]

Hey everyone,

I’m hosting my n8n instance on Elestio, and it’s been working flawlessly—until today.

I’m running a workflow that checks if a company has an spf.protection.outlook.com MX record. That part works just fine.

The issue arises with the Baserow node (which I also self-host). Here’s what’s happening:

I initially scraped data into a table named “XYZ 2011 - 2025”. Now I want to scrape into a different table: “XYZ 2000 - 2011”.

However, when I run the workflow, the execution still shows it’s writing to the old table (“XYZ 2011 - 2025”), even though I updated the node configuration.

Here are some screenshots for reference:

I’m going to restart the instance now, but I have no idea why this is happening.

Has anyone experienced something similar or have any ideas?

The ID doesn’t work manually, but I tried everything.

Thanks!

P.S. the RabbitMQ is connected to merger, the “clean up” function just messed it up visually.

[Noro]

It does it sometimes into the old and sometimes into the new table. What?

[Noro]

Now, after restarting it works.

But would still love to understand what caused the problem in the first place.