1. set a datetime-like value for a Parameter, in JSON. e.g.

{
  "last_modified_begin": "2021-12-12T12:12:12+00:00",
  "last_modified_end": "2021-10-10T10:10:10+00:00"
}

2. hit

DICT

3. Note that dates and times have changed 😞

4. hit JSON

5. note that dates and times are still changed

{
  "last_modified_begin": "2021-12-12T12:12:00+00:00",
  "last_modified_end": "2021-10-31T01:10:00+00:00"
}

currently checking that the original dates are used if I don't click those buttons...

I also asked the UI team, will get back to you

Thanks @Anna Geller

Would you mind sharing what timezone you are in?

thanks @Jenny

Hmm… I’m still not able to replicate that odd switch from 10 to 31 and I can’t see any obvious reason for it in the code. My guess is there's some oddity in time zone/and the moment.js library we're using. I’ll open a ticket.

For reference, this is Google Chrome Version 96.0.4664.110 (Official Build) (64-bit), on Win10, running on cloud.perfect.io

The incorrect results only occur for some months (05-10 - may-oct, inclusive), independent from the year. When calculating, if the result will be incorrect it takes much longer (2-3 minutes for 12 dates). Correct results come back instantaneously. Please see attached for the testing I've done. Hope it helps

dropping the tz adjust doesn't make any difference afaict, and the resulting json adds it back.

This is very strange and I still cannot replicate. Can I ask you for a bit more info/investigation? • Have you set your timezone from the user menu or is set at 'Local'? (You can find the timezone selector by clicking on the avatar in the top right corner and then selecting Account Settings and Profile). • If you explicitly set your timezone to GMT in the user menu, do you still see the odd conversions? I'm not convinced that the timezone is having an impact here since its from a date time string but I want to rule it out as it's the only thing that I can see that would explain you seeing this issue and me not being able to replicate it.