Bug in v0.216.0 : Datetime data being shown incorrectly

Questions
#1

Describe the issue/error/question

Datetime data seems to now been unnecessarily and incorrectly formatted before being output, which is causing issues like:

  1. being shown in the UI in a different notation from what it actually is, or
  2. shown as Invalid DateTime
Case 1.

image
image690×599 20.9 KB

The expected (correct) value here is the green-underlined data.

Case 2.

The input data as seen in the Schema mode:

image
image1107×651 25.5 KB

The same data as seen in Table mode:

image
image1310×587 28.3 KB

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 0.216.0
  • Database you’re using (default: SQLite): Postgres
  • Running n8n with the execution process [own(default), main]: default
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
#2

Rolled my instance back to v0.215.0 for now, where this issue isn’t manifesting.

#3

Hi @shrey-42 thanks for reporting this. I’ll make sure we take a peek and triage this :pray:

#5

Quick update: we’ve prioritized this bug and is currently sitting as one of the next tickets to be picked up by an engineer. No timeline yet, but hopeful for a relatively speedy resolution since you’ve confirmed it’s something that was added in 0.216.0 (not some existing, difficult to pin down bug).

Will keep this thread updated; and hopefully get you back on the latest version ASAP @shrey-42 .

4 Likes
#6

Another update: PR with the fix to revert to pre 0.216 behavior is merged and should be available in the next release.
Thanks @shrey-42 for reporting.

3 Likes
#7

New version [email protected] got released which includes the GitHub PR 5528.

2 Likes
#8

@shrey-42 when you get a chance to update, it would be very helpful if you could confirm that this issue is now resolved. Thank you!

#9

Hi @maxT .

Just checked. The 2nd case seems to have fully resolved now.

The first one, partially. Although, the formatting is now proper, for some reason, the ‘preview value’ underneath the input field is completely dynamic (updating in real-time), as opposed to being set to a fixed value at the time of the execution of the node. See:

#11

Hi @shrey-42, thanks so much for checking in. Do you think that the preview being in real-time is an issue or actually good? I can def. see that it might be confusing but also see that it’s the correct behavior because the value would be updated once you execute again. Would love to hear your thoughts.

#12

@Niklas_Hatje

Well, i would consider it to be an issue, given that i had already ‘executed’ the node. Post execution, i would want to see the execution result only.

Had i not executed it, it would still have made more sense for the preview to be real-time.

Maybe, when we expand the expression editor and then it shows real-time preview?

2 Likes
#13

Thanks so much for your feedback. I like the idea of only showing the rea-time aspect when it’s focussed.

1 Like