1 reply

Sorry for the confusion on this one! We'll investigate and see if there's a way we can handle it better.

The task was in a claimed state for too long (to the point where the Monitoring Service, running on the host server, thought "there has to be something wrong here"). Tasks can be in a "claimed" status either during the Revit model loading period - or, if multiple tasks are running on a single model, it may claim multiple tasks, open the model once, and then execute them in order (one task will be in progress while the siblings are still "claimed").

In any case- this happened because looking at it "from a distance" on the host server, the service was worried that it must be dead after 5 hours (marked as Error and sent the email). But in fact, the task server was still working on it (or its sibling tasks) - and 5 minutes after the monitoring service had given up on it, the task finally got its turn and finished up quickly- at which point it updated the task information with the actual data.

Best Regards,

Matt