Setup question // n8n on Render.com + Supabase backend: polling problem

Questions
1
Does anyone familiar with n8n's backend tech have an idea what service could be hitting Render, and whether this is a configuration that can be set off?

Information on your n8n setup

  • n8n version: → latest version
  • Database (default: SQLite): → Postgress on Supabase
  • Running n8n via (Docker, npm, n8n cloud, desktop app): → Docker, on Render.com
  • Operating system: → Ubuntu
2

Hey @Wicked_AI_Ware would you like to expand on this question, it is not clear what you are referring to.

3

Sure:

So, I have explained my setup - I hope that is clear.
Render (for free accounts) works in this way: it spins the n8n docker instance down after a few seconds of not using it.
It is then ONLY spins up again when a WF is used/needs it.

The problem is this:

  • I have ZERO active WFs (I use this environment to prototype)
  • I had not used n8n at all in June. The only activity as on June 12th to update the Docked image to the latest n8n version.

Despite this month of inactivity, I saw my Render.com quota was almost maxed out.
So something was off. I reached out o Render to ask for more info and they explained their systems get hit non stop.
Hence my question: anyone know if this is normal n8n backend behavior / whether this is configurable?

Is this more clear?

4

Wouldn’t render people know what was hitting the instance?