Anyone having issues adding 5 minutes to a DateTime?

[MultiTech]

For the past 10 min or so…

[12/28/2021 4:00 pm] + “000:05:00”

has been giving the following result:

• 12/31/1969 18:05:00

I’ve got a DateTime, and I’m trying to add 5 minutes to it.

• It’s been working all day, for ever since… liiiiike forever. But suddenly just now it stopped.

Not sure if it’s something I did, configuration wise… all I did was change a logic from [column] = ‘value’ to IsNotBlank([column])… shouldn’t have anything to do with that.

So yeah… 2+2=fish I guess

---

Anyone else?

[MultiTech]

And when I test elswhere… it works as it should. figures.

---

Not sure how I’m gonna debug this formula:

• Seems pretty straightforward to me…

[MultiTech]

Turns out it’s something to do with using UserSettings()

• I should have known NOT to use UserSettings(), but it’s just so… convenient some times.

But then you run into stuff like this - and that’s why I never use UserSettings

• It’s a see-saw bug; or more accurately… a collection of bugs associated with using data from UserSettings in various contexts and places around the app, which persistently reoccur after daily update deployments.

---

Problem Overview

The [Timestamp] column was successfully building a timestamp, but it’s date was coming from UserSettings().

• It seems that using the timestamp column was the problem.
  • My guess: the data from UserSettings wasn’t getting passed along due to some parralization problems on the backend.

---

Solution Overview

• Basically… hardcode things by ‘copying’ the formula from one into the other

• I took the original timestamp’s formula, and modified it to work for this subsequent timestamp.

---

hack hack hack… all day long… hack hack hack, while I sing this song…