Nested subworkflow getting cached in self-hosted workflow

Questions
1

I have a subworkflow calling a subworkflow. In that lowest level workflow, I discovered a bug where it’s not waiting for a file to completely download from google drive before processing it so I put in an await in the javascript node after the google drive node. When I run it, I can’t see the code change. But when I drop into the editor, I can. I just updated to the latest version and seeing the same problem. Note that if I run it from the intermediate level subworkflow, it works.

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 2.2.6
  • Database (default: SQLite): SQLLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: ubuntu (Hostinger VPS)
2

Hi @Michael_Toback,

Take note that with version 2 where the concept of publishing a new version is now implemented over the older Activate toggle, you must publish a new version again of your sub workflow for changes to take affect. Simply Saving the workflow is not good enough anymore

3

Thank you! Is there anything I can read or view that will explain this? I did see the publish but didn’t know what it was for, when to use it, etc

4

Yes sure, you can have a look at the documentation below. Did this solve your issue?

5

yes it did. There are more issues around design, but nothing I can’t figure out on my own. My problem is just understanding what changed and how 2.0 works.

Thank you!!

6

Please can you mark my response as the solution if this helped resolve your issue.

You can read more here to see what has changed: