Moving project does not move project in sharing settings

[fank]

Bug Description

Not sure how to describe this issue correctly, thats why I attached a lot of images to explain the issue.

Basically I can't call a workflow in the same project, due to permission issues when I moved it from another project.

To Reproduce

1. Create 2 projects
   

2. Create following workflow in project 1
   
   

Workflow JSON

{
  "name": "Trigger workflow",
  "nodes": [
    {
      "parameters": {},
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "id": "da85ad5a-a463-46c1-963e-da92f553a228",
      "name": "When clicking ‘Test workflow’"
    },
    {
      "parameters": {
        "workflowId": {
          "__rl": true,
          "value": "dtyYU2lB0OeyDJVZ",
          "mode": "list",
          "cachedResultName": "Test project 2 — My workflow 4"
        },
        "workflowInputs": {
          "mappingMode": "defineBelow",
          "value": {},
          "matchingColumns": [],
          "schema": [],
          "attemptToConvertTypes": false,
          "convertFieldsToString": true
        },
        "options": {}
      },
      "type": "n8n-nodes-base.executeWorkflow",
      "typeVersion": 1.2,
      "position": [
        220,
        0
      ],
      "id": "929ebc34-16b9-419f-adeb-e78f8fbc4a4a",
      "name": "Execute Workflow"
    }
  ],
  "pinData": {},
  "connections": {
    "When clicking ‘Test workflow’": {
      "main": [
        [
          {
            "node": "Execute Workflow",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "versionId": "a1f175c1-98cd-465c-bdb1-c35a24a64ef3",
  "meta": {
    "instanceId": "94a4722c99e67331d954b7292a159d350b5424049db5ee23fe2d0df7fe09b001"
  },
  "id": "RZAzIjhXw7KekE4C",
  "tags": []
}

3. Create following workflow in project 2
   
   

Workflow JSON

{
  "name": "Sub workflow",
  "nodes": [
    {
      "parameters": {
        "inputSource": "passthrough"
      },
      "type": "n8n-nodes-base.executeWorkflowTrigger",
      "typeVersion": 1.1,
      "position": [
        -140,
        0
      ],
      "id": "0e480812-7a7b-4737-bff7-1f492a495530",
      "name": "When Executed by Another Workflow"
    },
    {
      "parameters": {
        "options": {}
      },
      "type": "n8n-nodes-base.set",
      "typeVersion": 3.4,
      "position": [
        60,
        0
      ],
      "id": "d244cd27-d611-42c5-bd4e-7cdeca661b0b",
      "name": "Edit Fields"
    }
  ],
  "pinData": {},
  "connections": {
    "When Executed by Another Workflow": {
      "main": [
        [
          {
            "node": "Edit Fields",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "versionId": "5831d676-4081-4b1d-98ce-04746dc01d37",
  "meta": {
    "instanceId": "94a4722c99e67331d954b7292a159d350b5424049db5ee23fe2d0df7fe09b001"
  },
  "id": "dtyYU2lB0OeyDJVZ",
  "tags": []
}

4. Ensure the correct workflow is called in project 1, it needs to call the sub workflow in project 2.

5. Change the ".. can be called by" to following settings, to it can be called by another project:
   

6. Test it once, it should run perfectly fine:
   
   

7. Now move the trigger workflow from project 1 to project 2:
   

8. Change the "... can be called by" to same project, because both workflows are now in the same project right?
   
   

9. Then execute it again and notice its not in the same project:
   

Expected behavior

Workflow should be able to execute fine if in same project and allow workflows from the same project.

Debug info

core

• n8nVersion: 1.82.1
• platform: docker (self-hosted)
• nodeJsVersion: 20.18.3
• database: postgres
• executionMode: scaling
• concurrency: -1
• license: enterprise (production)
• consumerId: 03176d77-824f-4ef2-83db-39f7bc022c2f

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: s3

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/134.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-03-12T04:26:05.752Z

Operating System

docker (self-hosted)

n8n Version

1.82.1

Node.js Version

20.18.3

Database

PostgreSQL

Execution mode

queue

[Joffcom]

Hey @fank,

We have created an internal ticket to look into this which we will be tracking as "GHC-1156"

[Joffcom]

Hey @fank,

Solid steps to reproduce the issue thanks.

[fank]

This was one of the issues, which was easy to reproduce, the others are just pain 👍

[fank]

I just want to say even newly created workflow in the same project are not callable by the moved workflow.
the only workaround is to set the "callable by" to any.

[fank]

@Joffcom Is there any progress on this one?
Since we started onboarding more and more colleagues on n8n, and they started to move personal workflows into projects this issue comes up more and more.

[jcn8n]

Hi @fank just picking this up from @Joffcom as its currently with my team to fix. Sorry to hear you're still running into issues with this. We have a handful of fixes and enhancements we're working through for projects of which this is one of them, so I'd hope we'll be getting to this shortly.

I just want to say even newly created workflow in the same project are not callable by the moved workflow.
the only workaround is to set the "callable by" to any.

I couldn't reproduce this part of the issue you reported. I can only reproduce the issue when sub-workflows are specifically moved from the original project they're created in to the same one as the parent. If a parent and sub-workflow are created in the same project to begin with, there shouldn't be any issue with leaving the "This workflow can be called by" setting to "Only workflows in Project X" as this is the default they are created with. Let me know if you're having issues with that though and we can take another look. (I tested this on 1.94.0)

We'll certainly let you know once we've got a fix lined up for the main issue above though. Thanks again for reporting this.

[fank]

@jcn8n the sentence is maybe missing some context.

I just want to say even newly created workflow in the same project are not callable by the moved workflow.
the only workaround is to set the "callable by" to any.

This was related about creating a new workflow, but then calling the workflow which was moved.
New workflows are fine, as long as you don't interact with the moved ones.