[bug] node set

Questions
1

img 01

image
image1582Ă—1174 146 KB

img 02

image
image2464Ă—1128 263 KB

In my image 1 I have the time information, but when I run it the times are different, why does this bug happen?

Information on your n8n setup

Debug info

core

  • n8nVersion: 1.50.0
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.15.0
  • database: postgres
  • executionMode: scaling
  • concurrency: -1
  • license: community
  • consumerId: unknown

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

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

security

  • blockFileAccessToN8nFiles: false

Generated at: 2024-07-16T19:12:54.957Z

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hi @Ruan17,

Interesting result. Would you be ok to share your full node or workflow so we could test this out without having to copy the code by hand? :slight_smile:

You can do it by selecting the node(s) in your editor screen and pressing ctrl+c and the pasting it here inside the </> option

image
image1403Ă—155 14.1 KB

4

I replicated the same test, but now it’s working normally, that’s strange, but this isn’t the first time this has happened to me, a year ago, this happened to me, but if it happens again I’ll send the code here

5

Curious…

Well, happy that at least you have it working as intended again!
Let us know if this comes up again :raised_hands: