Somehow, I have ended up with Events containing <Seconds>60</Seconds>. I don't /think/ I entered them that way in the GUI -- but if I did, it let me. (I am 100% sure I didn't do any XML export/import hackery or any such thing to get them in there.) With the current version (8.2.4), I cannot edit those Events: it throws an exception. I have not tried editing those events in recent memory, and have upgraded VC a few times since creating the job containing them; so I have no idea how long this problem has been brewing....

Here's an example:

<FlowClass>
<Id>4775ab8c-d0fa-4eb6-9ad5-d393bdc89a3d</Id>
<ActionType>RetryTask</ActionType>
<RetryFailAction>StopJob</RetryFailAction>
<TimeOut>
<Hours>0</Hours>
<Minutes>0</Minutes>
<Seconds>0</Seconds>
</TimeOut>
<EventType>OnError</EventType>
<EventCondition>Always</EventCondition>
<ValueType>String</ValueType>
<ConditionType>Equal</ConditionType>
<ConditionValue1 />
<ConditionValue2 />
<Minutes>9</Minutes>
<Seconds>60</Seconds>
<NotificationId />
<TaskId />
<JobId>4742a4a2-fe06-46fe-908a-ae81bdf8bbcf</JobId>
<RunJobAsynchronous>false</RunJobAsynchronous>
<DeactivateJob>false</DeactivateJob>
<RetryTimes>6</RetryTimes>
<RunFollowingTasks>true</RunFollowingTasks>
<DeactivateTask>false</DeactivateTask>
</FlowClass>

I have been able to work around the problem by exporting the Job XML, editing it, and reloading it (e.g., changing 9 and 60 to 10 and 0 in the above).

But I think your GUI should be more tolerant of such legacy configuration issues.

Thanks much.

I guess you have checked the audit log?

I saw nothing relevant in the Audit Log -- but then, it looked like a Client-side problem. Here is the traceback from the Error Handler window (my apologies for not including it previously):

System.ArgumentOutOfRangeException: Value of '60' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at UCJobFlow.OHMDIECAKCEELBCIECIGJLCONDGOJGCNEGDJ() in C:\sourcefiles\code\VisualCron\Flow\UCJobFlow.vb:line 124
at UCJobFlow.Init(FlowClass tf, JobClass j) in C:\sourcefiles\code\VisualCron\Flow\UCJobFlow.vb:line 33
at frmAddEditJobFlow2.OHMDIECAKCEELBCIECIGJLCONDGOJGCNEGDJ() in C:\sourcefiles\code\VisualCron\Flow\frmAddEditJobFlow2.vb:line 8
at frmAddEditJobFlow2.JNFMMNBLKNDHOINIOJJECPNMEDBNPKNFKMMJ(Object , EventArgs ) in C:\sourcefiles\code\VisualCron\Flow\frmAddEditJobFlow2.vb:line 30
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Thanks for the report. We have increased the default values here for the next build. You can use 1 hour instead of 60 minutse for now.

---

What is this timeout?

You mean increased from 60 seconds to 1 hour?

Hi, al355. The value in question is not a timeout; it's the wait time between retries if a job or task fails. I had intended a wait time of 10 minutes, but somehow (my fault or VC's fault, no way to know at this point) it had been stored as 9 mins, 60 secs. The GUI Event Editor was not able to display that, and threw an exception.

Hi, Support. I'm not sure what you mean by "increased the default values": the problem has nothing to do with defaults, as far as I can see. I am quite happy to enter 1 hour instead of 60 mins, or 1 min instead of 60 secs, going forward. The problem is that values of 60 secs and 60 mins that (somehow) got in there previously are breaking the GUI now. IMO, the GUI should be able to display them, and ideally even normalize them automatically, but in any case not throw an exception. (If what you meant was "we have increased the /limit/ values" then I understand you, and that sounds like a reasonable solution.)

Thanks much. -Dean