Hello,

I'm using the VisualCron API for a web interface, and I'm using TimeClass.InitDate to get and set the startdatetime. I noticed that TimeClass.InitDate gets updated each time the task has run, which I didn't expect to happen and can be a bit confusing when editting a task. Is this expected behavior or should I get the original startdatetime from another property?

Regards,
Patrick

InitDate is updated automatically. You should use Trigger.FirstRun property to control when it should start the schedule.

---

That's what I tried before using TimeClass.InitDate, but when I tried updating Trigger.FirstRun it didn't affect the next run date so I switched to TimeClass.InitDate. Should I set both when updating the start time of a job through the API?

What I think might work for me is this: when getting the time, use Trigger.FirstRun and when setting the time, use both Trigger.FirstRun and TimeClass.InitDate. Any problems with that approach?

InitDate gets Datetime.Now when the Trigger is created - don't you get this value?

---

Yes I do, but my thought was that it might look confusing to set a trigger to a certain datetime but later when editing it, the time has changed. That's why I was thinking I could just display the FirstRun time but also set InitDate when a job is updated.

On the other hand, this will have adverse results if a job is editted with the client instead of my web control so I guess I better just stick to InitDate exclusively.