I loaded 10.33x last night (before the end of the month local time) and this morning (April 1) I found an error on the way %mcoldestdayonrecord% was being reported. See attached photo:
with the start of the new month, the value is set very high/low to be beaten by your next data from the station…by 6pam/6am it will be updated 