Bug: Gmail Node is not saving parameters

[dvlexp]

Bug Description

I'm tryng to use Gmail Node to Add and Remove labels of emails, but then I filled in that parameter if I close the node setup its information despair. Here is a quick video about that.
VIDEO

To Reproduce

I don't know yet

Expected behavior

It just need to save info

Operating System

Cloudron

n8n Version

1.40.0

Node.js Version

2.1

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @dvlexp,

This should be fixed in 1.41.0 can you upgrade and let me know if you still see the issue?

[dvlexp]

Hi Jon, I’ve tried to update my n8n version, but it is returning the message “Not new updates available”. What can I do in this case, please? ***@***.*** De: Jon ***@***.***> Fecha: viernes, 10 de mayo de 2024, 21:14 Para: n8n-io/n8n ***@***.***> CC: dvlexp ***@***.***>, Mention ***@***.***> Asunto: Re: [n8n-io/n8n] Bug: Gmail Node is not saving parameters (Issue #9366) Hey @dvlexp<https://github.com/dvlexp>, This should be fixed in 1.41.0 can you upgrade and let me know if you still see the issue? — Reply to this email directly, view it on GitHub<#9366 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BINF6FVC7ZUUGXD3KGPJLRDZBVPHBAVCNFSM6AAAAABHRLQ4MWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGQYDANRZGE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Joffcom]

Hey @dvlexp,

You would need to set the docker image to 1.41.0 manually in Cloudron if it allows this. This is the PR that fixes this issue: #9324

For now I am going to mark this as closed, If after updating you still see the issue let me know and we can open it again.

[dvlexp]

Thank you! De: Jon ***@***.***> Fecha: lunes, 13 de mayo de 2024, 03:47 Para: n8n-io/n8n ***@***.***> CC: dvlexp ***@***.***>, Mention ***@***.***> Asunto: Re: [n8n-io/n8n] Bug: Gmail Node is not saving parameters (Issue #9366) Hey @dvlexp<https://github.com/dvlexp>, You would need to set the docker image to 1.41.0 manually in Cloudron if it allows this. This is the PR that fixes this issue: #9324<#9324> For now I am going to mark this as closed, If after updating you still see the issue let me know and we can open it again. — Reply to this email directly, view it on GitHub<#9366 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BINF6FVHRMLW7BMHSOKVN2LZCBOZRAVCNFSM6AAAAABHRLQ4MWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWG43TMNZXGA>. You are receiving this because you were mentioned.Message ID: ***@***.***>