I'm having a great deal of trouble with K2.Net 2003 trying to use SetStartRule for a delayed execution of a WebService-poll.
My process is supposed to check a webservice (which again checks a db for a certain value remote) every 10 min. from now until either the value is correct or it has been more than 100 retries.
The retry works sort of, but the problem occurs whenever the time passes midnight.
I'm using something like this :
K2.SetStartRule((int)K2.ProcessInstance.DataFields["RetryDays"].Value, (int)K2.ProcessInstance.DataFields["RetryHours"].Value, (int)K2.ProcessInstance.DataFields["RetryMinutes"].Value, (int)K2.ProcessInstance.DataFields["RetrySeconds"].Value);
where RetryDays, RetryHours, RetryMinutes and RetrySeconds are all ints in datafields for the process. For this particular part of the process all of them are 0 except RetryMinutes which is 10. (10 minutes)
The retry works quite good, and tries again every 10th minute until midnight. The last four entries in report for activityinstance :
WaitForActivated | 12.03.2008 23:25:45 | 12.03.2008 23:25:49 | High | Completed | 00:00:00:04 | |||
WaitForActivated | 12.03.2008 23:35:49 | 12.03.2008 23:35:49 | High | Completed | 00:00:00:00 | |||
WaitForActivated | 12.03.2008 23:45:49 | 12.03.2008 23:45:49 | High | Completed | 00:00:00:00 | |||
WaitForActivated | 12.03.2008 23:55:49 | 12.03.2008 23:55:54 | High | Completed | 00:00:00:04 |
It should have continues 13.03.2008 00:05:49 but it does not... it just stops, still active. No error message, or anything.
Anyone know if there are something wrong with K2.Net 2003 and SetStartRule? Doesn't it support SetStartRule spanning over days? Or is it just a plaint math-bug in the Datespan-functionality in K2.Net?