Warn the user when scheduling a deployment before the current time Hot

by Kevin Dimmen on June 01, 2016

I just ran into an issue where I wanted to schedule a deployment for the following day, and I had the time of day correct but the actual date wrong, which ended up causing the deployment time to be before the current time.  This caused the deployment to start immediately rather than being scheduled. While this makes sense from a time perspective, it's not what I wanted to have happen.

It is 100% my fault, but it would be nice if I was warned when scheduling a deployment and the deployment time pre-dated the current time.  Then I could see that I was telling the system to do something that was most likely wrong, and I could fix it before unintentionally having my process app deployed immediately.  Or if I was a bonehead, and I was intentionally scheduling a deployment for the past, I could confirm that I was doing something stupid before continuing.

PrintEmail

Recent Tweets

Twitter response: "Invalid or expired token."