1

Task Queue Not Reflecting Active Tasks

Our Clarity environment has been running into what seems to be a task saturation issue lately, meaning we have too many tasks in the queue each day for our task machines to complete before they time out in a "New" status. Around 70% of our tasks each day are timing out at this point.

I would expect this if I had suddenly added a heavy load of projects at some point, but I have not. This issue of tasks not being run on time just popped up around the time where we updated from Clarity 2022 to 2022.1.

During troubleshooting I've found that the task queue is not properly tracking which tasks are "Claimed" or "InProgress." I found this morning that we have 16 tasks currently running on the task machines and only 4 showing as either "Claimed" or InProgress" in the queue on the web portal. I'm wondering if this is related to our task saturation/timeout issue?

Honestly at this point I am considering setting all tasks to "Disabled" through a SQL query and going through project by project and shuffling things around then starting them up again one by one. Hopefully this would help get things running again. 

Follow

2 replies

Votes Newest Oldest

Holden,

I believe the support team is still working on this one - sorry I've been buried.

My suspicion is that Revit is getting hung up, but not in a way that we can recognize and kill it on the task server. As a result, the host side monitor sees that it has been in-progress too long, and marks the task as Errored out. This causes it to immediately drop off the list of current tasks - even though Revit still might be open.

This is what we're pursuing.

-Matt

Comment

I took the nuclear option and set myself a project for the month of January to stop all tasks and set them up one project at a time to see if I can spot issues I couldn't see before. So far I have been able to resolve a few project sized in scope issues through the process, but the above mentioned issue remains.

I heard back from Matt at the beginning of the process. He reported that this is something of a known issue to him. A task gets stuck while running on the task machine (all the instances I've seen are either a model freezes while opening, or the "Requested service is not available" pop-up locks up Revit and Clarity doesn't resolve it), after a certain amount of time the Clarity host will kick the task out of the "Current Tasks" queue (but not into the "Completed Tasks" queue from what I've seen), but the task will remain stuck on the task machine, ignoring the timeout limit set in the host and continuing to hold up that Revit session until it is force quit or the computer is restarted.

I am submitting a separate ticket for this as I have stopped hearing back from Matt.

Comment
Reply