Can't unpin output in HTTP module

[leesilverman]

Bug Description

I pinned some data in the HTTP module. Now that I've finished debugging, I can't unpin it.

Debug Info:

Debug info

core

• n8nVersion: 1.49.0
• platform: npm
• nodeJsVersion: 18.19.1
• database: postgres
• executionMode: regular
• concurrency: -1
• license: community
• consumerId: unknown

storage

• success: all
• error: all
• progress: true
• manual: true
• binaryMode: filesystem

pruning

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

security

• secureCookie: false

Generated at: 2024-07-15T18:57:26.789Z

To Reproduce

1. Open HTTP Module
2. Select "Enter Mock Data"
3. Paste in some JSON
4. Execute the workflow
5. Re-open the module.
   
   
   

Expected behavior

There should be an "un-pin" option in the dropdown and in the editor when the module is open.

Operating System

Ubuntu Linux 24

n8n Version

1.49.0

Node.js Version

18.19.1

Database

PostgreSQL

Execution mode

main (default)

[Joffcom]

Hey @leesilverman

What happens if you click on the pin icon and click on unpin at the top?

[leesilverman]

That's the problem. There is no unpin option on top when I open the module. I just tried duplicating the module thinking that might clear whatever's wrong, but no luck.

I also tried with a different HTTP module in the same flow, and that DOES have an unpin option when I pin some data.

I can send you the flow in a DM, but there's some private info / access keys hardcoded in so I don't want to post in this thread.

[Joffcom]

Hey @leesilverman

That is unusual for it to appear in one http request node and not another. If you go to the settings for the node which node version is it using?

[Joffcom]

Hey @leesilverman,

I have worked it out, We don't yet support pinned data for multi output nodes. I suspect the node data was pinned before you set the error output and that is why it can't be removed. If you toggle back to one of the other modes in the settings it should allow it to be unpinned.

Internal bug reference is ADO-2343

[janober]

Fix got released with [email protected]