Bug: Pinned data on this node is corrupted and can't be displayed

Questions
,
1

Describe the problem/error/question

Since 2.22.0 this happens:

“Pinned data on this node is corrupted and can’t be displayed.”

Out of a sudden running a workflow this statement appears, even though data has never been pinned.

It happens totally random and is not reproducable

What is the error message (if any)?

“Pinned data on this node is corrupted and can’t be displayed.”

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.23.0
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): queue
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: was linux ami
3

@Kool_Baudrillard , can you revert to 2.21.7? 2.23 is still beta

4

@Kool_Baudrillard does it hit specific workflows or randomly across all of them? and can u export one of the affected workflows as JSON and look at the pinData field — empty {} is normal, anything weird in there points at corruption left over from an upgrade migration.

5

Tottaly random I can’t reproduce it, an actual workflow where it happened:

“pinData”: {},
“connections”: {
“When clicking ‘Execute workflow’”: {
“main”: [
[
{
“node”: “Select rows from a table”,
“type”: “main”,
“index”: 0
}
]
]
},
“Select rows from a table”: {

6

yeah, I know and it´s my personal env, where it´s not critical. However I assume this will affect aswell others

7

Since pinData is showing as {} , I’d try to capture the next occurrence rather than guessing from this export alone. If it happens again, could you note the exact node name, whether it appears right after opening an old execution or during a fresh run, and grab any browser console or server log errors around that time? That would make it much easier to tell if this is saved workflow state or the editor UI getting confused.

8

good morning @Kool_Baudrillard
can you please share your json?