Issues with Renaming Workflows in n8n

Other Questions N8n
1

I deployed n8n via docker compose; while I can create, execute, and delete workflows, renaming them is not possible. See the revised configuration below. What setting might be preventing name changes?

version: '3.8'
services:
  workflow_service:
    image: n8nio/n8n:stable
    ports:
      - "8080:5678"
    environment:
      - ENC_SECRET=xyz987
      - COOKIE_SAFE=false
      - AUTH_ENABLED=true
      - AUTH_USER=admin
      - AUTH_PASS=pass123
      - PROTOCOL=https
      - HOOK_URL=https://example
      - DATABASE=postgres
      - PG_DB=workflowdb
      - PG_HOST=db_service
      - PG_PORT=5432
      - PG_USER=admin
      - PG_PASSWORD=pass123
    volumes:
      - service_data:/home/node/.n8n
    depends_on:
      - db_service
  db_service:
    image: postgres:15
    environment:
      - POSTGRES_DB=workflowdb
      - POSTGRES_USER=admin
      - POSTGRES_PASSWORD=pass123
    volumes:
      - db_data:/var/lib/postgresql/data
volumes:
  service_data:
  db_data:
2

I had a similar experience after deploying using Docker Compose. For me, the issue turned out to be related to a persistent configuration in the user data directory that may not have been refreshed on subsequent image updates. I resolved this by completely clearing out the volume and starting fresh, which seemed to remove lingering permission issues affecting the workflow names. It might be worthwhile checking if any updates have changed how environmental variables interact with the file system, especially since device authentication settings can sometimes result in unexpected restrictions on renaming.