I would also maybe try relaunching Mango from the command line and watching for any errors that occur when you try to view a watchlist that has this problem, if it persists through a restart.

@pascal are you talking about Excel reports?

The cron expression should be evaluated against the server timezone AFAIK (it uses the timezone from the OS/JVM by default, you can override this in your env.properties file).
Are you sure you don't have your server timezone set to UTC?

@pascal said in Use of CRON to schedule reports.:

What is the behavior of the CRON expression when DST (daylight saving time) adjustments apply

Good question. Our cron code is based on the Quartz scheduling library v2.1.0, so this should help -
http://www.quartz-scheduler.org/documentation/faq.html#FAQ-daylightSavings

Of course if its actually evaluating the expressions as UTC time then there is no DST.

Hi philgdep,

Ah okay. No deleting that class file is the beginning and the end of solving that issue (well, you probably already had to restart Mango) What slowed down?

One of the lowest hanging fruits to speed up a Mango is to change the database stream type in the env.properties file. Try setting

db.nosql.shardStreamType=MAPPED_BYTE_BUFFER

in env.properties and restarting.

Also note that if you are using the NoSQL database part of Mango enterprise it will prevent duplicate values from happening.

If you still can't make sense of it just send me the strings you used for both formats, I can check them against my test Mango.

I also think that you just need to edit your point template and set Logging to "when point value changes". I don't think there's anything else you would need to do.