$getWorkflowStaticData is not defined

[remi-bartas-hc]

Bug Description

Hi, I have switched today from The n8n version (v1.46.0) on my headchannel workspace as I have been prompted that it soon will end its lifetime to the latest stable version.

Unfortunately, all of my workflows stopped working, as I get the $getWorkflowStaticData is not defined error.

I have built many workflows in the past, using a lot of Code nodes in each of them. In those nodes, I was using the mentioned function to save some important information and easily access them. I never had any issues with testing the flows manually, which apparently changed in the latest version. Moreover - even when I tried running them on Schedule or triggered via the webhook, it still produces the same error.

I hope there is an easy way to fix all my workflows.

I am sending a few of them with the problems I mentioned:
https://headchannel.app.n8n.cloud/workflow/MVKdqjKE7bLb4nyX/executions/45778
https://headchannel.app.n8n.cloud/workflow/wcHpGQn8DSDK7UvK/executions/45789
https://headchannel.app.n8n.cloud/workflow/bNqiH902xAxWlPEo/executions/45799
https://headchannel.app.n8n.cloud/workflow/wpz3HiMVxnUTJPdW/executions/45797

To Reproduce

1. Review historical executions of the flows:
   https://headchannel.app.n8n.cloud/workflow/MVKdqjKE7bLb4nyX/executions/45778
   https://headchannel.app.n8n.cloud/workflow/wcHpGQn8DSDK7UvK/executions/45789
   https://headchannel.app.n8n.cloud/workflow/bNqiH902xAxWlPEo/executions/45799
   https://headchannel.app.n8n.cloud/workflow/wpz3HiMVxnUTJPdW/executions/45797

Expected behavior

At least, to fix the issues when the workflow is triggered on schedule and via Webhook.
Ideally, allow using the same concept while manually testing the workflow (as it used to work), as it would make things a lot more complicated to have to always test it via sending a webhook trigger.

Operating System

Cloud

n8n Version

latest stable (1.70.3)

Node.js Version

.

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @remi-bartas-hc,

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

[riascho]

Hi @remi-bartas-hc
this is likely due to the new task runner feature. We've disabled that for your instance for now, so your workflows should be working again, while we fix this bug internally.
Let us know if you're still seeing issues related to it.

Thanks!

[remi-bartas-hc]

Hi Ria, I'm happy for you to take a look at my instance during the time needed to solve the issue. Thank you. Best regards, Remi

[remi-bartas-hc]

Hi, I have checked this morning and all seems to be working fine now Thank you

[MikaelX]

We have the same on our on-prem instance running version: 1.70.3

Now you just have to trust me that the data is there normally :)

[riascho]

Hey @MikaelX

Thanks for reporting this! Although I have never seen a return like this.

It does work if you assign the global static property inside the json.

// initialize staticData object
const workflowStaticData = $getWorkflowStaticData('global');

// if (!workflowStaticData.hasOwnProperty('Answers')) {
//   workflowStaticData.Answers = '42'
// }

return [
  {
    answers: workflowStaticData.Answers
  }
]
  ;

[janober]

Fix got released with [email protected]