N8n Backend MySQL Crash After Docker Restart — TRUNCATE on webhook_entity Causing Issues

Questions
1

Hi n8n team/community,

We encountered a critical issue with our n8n instance and are seeking some clarity regarding a table named webhook_entity.

Context:

  • We recently upgraded MySQL from v8.0.36 to v8.0.42.
  • Post-upgrade, n8n was functioning normally.
  • Later in the day, we restarted the n8n Docker container to add a new node dependency in the Docker JSON file.
  • Immediately after the restart, both n8n and the backend MySQL container started crashing continuously.

Observation:

  • n8n logs didn’t show any clear errors.
  • However, MySQL logs captured this repeatedly:
We intentionally generate a memory trap.

Query (7184f975b030): TRUNCATE TABLE webhook_entity
Connection ID (thread ID): 64
Status: NOT_KILLED

N8n docker Log

{"log":"    at Socket.emit (node:events:513:28)\n","stream":"stdout","time":"2025-05-14T08:27:29.690501084Z"}
{"log":"    at Socket.emit (node:domain:489:12)\n","stream":"stdout","time":"2025-05-14T08:27:29.690504164Z"}
{"log":"    at TCP.\u003canonymous\u003e (node:net:301:12)\n","stream":"stdout","time":"2025-05-14T08:27:29.690507124Z"}
{"log":"Last session crashed\n","stream":"stdout","time":"2025-05-14T08:27:34.580682317Z"}

N8n UI:

Screenshot 2025-05-14 at 3.50.12 PM
Screenshot 2025-05-14 at 3.50.12 PM653×193 12.8 KB

Our Questions:

  1. What is the exact purpose of the webhook_entity table in n8n?
  2. Why is n8n issuing a TRUNCATE TABLE webhook_entity query on startup or during runtime?
  3. Could this TRUNCATE be causing a crash in MySQL (or the schema/table being locked)?

Information on your n8n setup

  • n8n version: Version 0.225.2

  • Database (default: SQLite): MySQL

  • n8n EXECUTIONS_PROCESS setting (default: own, main): own

  • Running n8n via (Docker, npm, n8n cloud, desktop app): : docker

  • Operating system: Ubuntu 22.04.2 LTS