I've heard comments before that timers in workflows can impact system
performance significantly. I don't have a good feel for the real world
impact though.
I would appreciate feedback on the issue so my team can evaluate options
around a problematic workflow.
The current issue:
A workflow was set up for a soft type of WTDocument that has a timer
which is left running to trigger the first task in the workflow again as
a "time to review" reminder after 3 years or so (based on a date entry
in a soft attribute). The timer was set up to check once per minute
initially and we have several running like that already (..and the
workflow had debug code sending "System.out.println" notes to the
background methodserver log <wince>).
I'm bothered in general by the idea of a timer that loops back on the
workflow for the current revision of a doc after several years, but I
can more easily argue the impact of leaving lots of running timers for
something that needs to be reviewed years later. I'm getting pushback on
removing the timer, and on fixing the currently running workflows so
they don't have the once per minute check with debug logging.
Thanks for suggestions and input. I'll post a summary of the feedback on
workflow timers to the forum for replies I receive.
-=wes
