When does the migration report update

Questions
1

Describe the problem/error/question

I’ve updated several workflows to use /home/node/.n8n-files instead of my legacy directory. They seem to be executing fine, but the migration report is still calling out these workflows.

Please share your workflow

Information on your n8n setup

  • n8n version: 1.123.6
  • Database (default: SQLite): postqreSQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu 22.04 LTS
2

Hi @russellkg ,

You should be able to still use your legacy path by setting this env var to allow access to the folder:

N8N_RESTRICT_FILE_ACCESS_TO=/legacy/path/
3

I think it was just as easy to change the mapping in docker-compose.

I’d still like to know why, after updating the paths within the workflow, the migration report still shows the same errors.

-Russ

4

I am not too familiar with how the migration tool evaluates workflows. Perhaps @Jon has more insights?