I have a couple of questions about threads:
1. What does the information in this window mean? I have nothing running btw so I'm
especially wondering what the TaskManagerCountOfThreads field is about - http://i.imgur.com/rfSgpAN.png
2. Why do templates not start sometimes? This is happening a lot more lately and is very frustrating. I run a
template a few times and a while later I try to run it again and nothing starts. Unlike the instant success bug posted
about HERE the bar does not shoot to finished with logs saying the template is done straightaway but instead it just
sits there with no instances loading, no logs and no successes etc. The only way to run the template again is too delete it from ZP and add it back in again.
3. This is about instances and buttons. So the stop button. When I stop a template it continues with
running the current threads until they are completed. When I press stop I nearly always want the threads
to be killed immediately instead of continuing in the background etc. Before someone suggests the idea of
manually closing every instance and then clicking yes in every confirmation window please don't because it
makes no practical sense.
I do agree that sometimes it is useful to have the threads finish off but often times
I want to stop/kill them so the best solution is probably to add a separate kill button.
Next is the interrupt button. It seems to act like a Pause button but in my testing when I "interrupt" a template
the instances pause but after pressing start again the instances don't seem continue from where they are paused,
instead the instances are killed. If there are more executions they start up instead. I've seen it act very differently
to this as well btw so I'm not really sure how its meant to function?
Cheers
1. What does the information in this window mean? I have nothing running btw so I'm
especially wondering what the TaskManagerCountOfThreads field is about - http://i.imgur.com/rfSgpAN.png
2. Why do templates not start sometimes? This is happening a lot more lately and is very frustrating. I run a
template a few times and a while later I try to run it again and nothing starts. Unlike the instant success bug posted
about HERE the bar does not shoot to finished with logs saying the template is done straightaway but instead it just
sits there with no instances loading, no logs and no successes etc. The only way to run the template again is too delete it from ZP and add it back in again.
3. This is about instances and buttons. So the stop button. When I stop a template it continues with
running the current threads until they are completed. When I press stop I nearly always want the threads
to be killed immediately instead of continuing in the background etc. Before someone suggests the idea of
manually closing every instance and then clicking yes in every confirmation window please don't because it
makes no practical sense.
I do agree that sometimes it is useful to have the threads finish off but often times
I want to stop/kill them so the best solution is probably to add a separate kill button.
Next is the interrupt button. It seems to act like a Pause button but in my testing when I "interrupt" a template
the instances pause but after pressing start again the instances don't seem continue from where they are paused,
instead the instances are killed. If there are more executions they start up instead. I've seen it act very differently
to this as well btw so I'm not really sure how its meant to function?
Cheers
