Dear all,

I have a state machine workflow hosted under asp.net 2.0 which uses the ManualWorkflowSchedulerService, as recommended. It also has persistence and tracking running, with UseActiveTimers="true", so that expiring Delay activities wake up the workflow and continue execution. Generally, this all works fine.

I have put up a test version of the web site and asked a colleague to test it across the internet. We were mystified by the fact that certain events which should have taken place when a Delay expired at a specific time actually took place much later.

I have now realised that the expected events do not fire because the web site has "gone to sleep" because nobody is accessing it. The events get fired the next time somebody accesses the web site, instead of at the scheduled time.

Does anybody know how to make sure that the web site "stays awake", so that the events on Delay expiry take place when they should?

Dear Jon,

Thanks for the suggestion. I checked the settings and the following were:

Recycle worker process (in minutes): 1,740

Shutdown worker processes after being idle for (time in minutes): 20

I have turned both these options off. Does that look like the right thing to do?

Dear Jon,

Thanks for your suggestions on this.

I can now confirm that the problem of late events is resolved.