[BUG] Next Run Date calculation error about mage-ai

[johnson-mage]

@geoff-rathmell So there are some limitations on the next run preview text for the cron expression when the time is displayed in the local timezone. We always store the dates in the metadata db in UTC, but we convert the UTC time to the local time on the frontend. Right now, only the minute and hour values (without special characters) can be used to accurately convert the cron expression to a human readable expression (in local time). If another value is included (e.g. the mon in 0 23 * * mon), it is based in UTC time, which is why the next run date seems off. There's an explanation in the Note underneath the input. We haven't been able to prioritize handling the day/month/week values in the cron expression for the human readable text conversion yet, but you can create a new feature request on github so we can keep track of it and put it on our roadmap. Hope this clears things up.