We are not able to get a response from support. We can't add flow, or open some flows in our n8n production instance

Questions
1

We are doing a self hosted instance of n8n, with postgreSQL. When we try to add new flows or projects, or open a few of the older flows in our system. we get errors. How do we get support for this?

2

Self-hosted production with Postgres, and both new flow/project creation plus a few old flows failing, points to a shared editor/API path rather than one broken workflow.

Post the first failed request from browser Network when you click New Workflow or open one broken workflow: endpoint, HTTP status, and one error line. No workflow JSON or credentials needed. n8n version plus whether Postgres changed recently is enough to separate UI/editor from database or permissions.

3

Hi @dihde

If your organization is on an Enterprise plan, you have access to dedicated support channels (usually via email or a dedicated portal) with guaranteed SLAs.

  • Where: Check your billing dashboard or contact your n8n account manager.

Since you mentioned errors when adding/opening flows in a PostgreSQL setup, you may want to check these three common culprits:

  1. Database Disk Space/Quota: If your PostgreSQL disk is full or has reached a quota, n8n will fail to write new flows or project metadata.
  2. Database Locks: If a migration failed or a process hung, you might have “zombie” locks on the workflow_entity or project tables.
  3. Memory Limits: If you are running n8n in Docker, ensure the container has enough RAM. Opening large flows can cause the process to crash if the memory limit is too low.

Please provide the following:

  • The output of docker logs [container_name] (if using Docker).
  • The PostgreSQL error logs (look for FATAL or ERROR entries).
  • The exact error message shown in the n8n UI (e.g., “Internal Server Error” or a specific 500 error).
  • What is the n8n version and the type of install