One of my APIs suddenly broke, and I discovered that if I evaluate

   Block[{$DateStringFormat = "ISODateTime"},
    DatePlus["2021-09-20", 1]

In my Desktop I get:


In Wolfram Cloud I get:

cannot be interpreted as a date or time input or as a date string format

Small question: It's a bug in this release? Or a compatibility change?

Big Question: Can I choose my cloud version, to avoid this kind of broke?


  • In my desktop I have the \$Version = "12.3.0 for Mac OS X x86 (64-bit) (May 10, 2021)"
  • In Wolfram Cloud \$Version = "12.3.1 for Linux x86 (64-bit) (June 24, 2021)"
  • $\begingroup$ I would guess the answer to the edited question title to be "No". I don't reproduce when I evaluate on the cloud: i.stack.imgur.com/7B7gT.png $\endgroup$
    – Jason B.
    Sep 29, 2021 at 15:55
  • $\begingroup$ @JasonB. I messed the $DateStringFormat line. Can you check again? $\endgroup$
    – Murta
    Sep 29, 2021 at 16:02
  • $\begingroup$ In that case, I get the same error in desktop 12.3.1 as I do in the cloud. $\endgroup$
    – Jason B.
    Sep 29, 2021 at 16:06
  • $\begingroup$ As a workaround you can create an intermediate DateObject via DateString[DatePlus[DateObject["2021-09-20"], 1], "ISODateTime"] $\endgroup$
    – Jason B.
    Sep 29, 2021 at 16:10
  • $\begingroup$ @JasonB. The major problem is that I can't have control over the version my code is running. So it's very easy to have a compatibility break, like this case. The my API just stoped $\endgroup$
    – Murta
    Sep 29, 2021 at 16:16


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.