Skip to Content
Former Member
Oct 02, 2013 at 10:37 AM

How to prevent [not responding] state for too long ?



We have some batch processes that could be very long, like several hours.

To complete them, customers have to launch it at the evening before to go home.

In Citrix environment, it seems that the process is killed if it stays too many time in a "not responding" state.

What is the good way to respond to Windows, to tell him the application is fine but still working ?

I don't want the user to be able to interact neither, so I doubt about Yield().

Is there a better solution ?