How to effectively check for n8n full readiness?

Questions
1

Describe the problem/error/question

I’m running n8n on Cloud Run with the minimum number of instances set to 0 and want to keep that default to keep costs as low as possible.
I’ve configured my startup probe to check for a successful response at the path “/healthz/readiness”, but I’m getting “Cannot GET” errors every time my Cloud Run instance warms up. However, it will work after a few seconds. It seems like this path is only checking the status of the database connection, but not the full readiness of n8n.
How can I check the full readiness of n8n to avoid this situation? I don’t mind if it takes a minute or two for n8n to fully start, but I just don’t want to have to implement some sort of retry on every client that will consume my n8n instance to handle this.

What is the error message (if any)?

Cannot GET /{path}

Information on your n8n setup

  • n8n version: 1.91.1
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Not set
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker / Cloud Run
  • Operating system: Official n8n Docker OS
2

I recommend to check api access by apikey. This ensures that n8n is completely operational.

We use this method to do database health checks using
N8n Hackers for our clients.

You can do full instance availability by creating a free account in the service.

3

Thanks for you answer! It inspired me, but I ended up using another approach: I set the N8N_METRICS variable to true and changed my startup probe to watch for the /metrics endpoint. It worked well!

1 Like
4

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