n8n deployed using Docker Compose runs fine, yet renaming workflows is blocked. Below is a revised deployment setup:
version: '3.1'
services:
workflowService:
image: custom/n8n_mod:stable
environment:
- ALLOW_RENAME=false
In my experience working with n8n deployments, the behavior being observed is consistent with how the software handles workflow names based on the environment setting. Setting ALLOW_RENAME to false is meant to enforce immutability of workflow names, likely to prevent accidental modifications after your workflows are in production. If renaming is a requirement for your use case, you might consider allowing it by changing the variable to true or removing it altogether. Ensure that you consult the latest n8n documentation as container behavior can vary between versions.