Hey João,
I've set my queue limit to around 20 tasks, but I still get that message now and again warning me that I've reached the limit of tasks in memory and no more tasks will be added to the queue. I'm not always sure what the problem is.
Is there any way to produce a log of the queues currently in memory which includes the name of each task and the number of seconds the task has been in progress?
Many thanks as always!
Yes that's of some help, but it still seems a bit difficult to pinpoint the task which caused the queue "pile-up" in the first place as %TRUN returns a whole list of tasks, most of which will be "innocent" and I thought I could try and identify the "guilty" if I knew how long it had been in the queue for.
It usually seems to be an Autowear task that causes these queue pileups, but CalendarTask has caused me problems also.
Ah I see. Maybe the runlog can be of help there then?
Does maybe the %TRUN variable help?
