Devart Forums

On two separate occasions over the last few months, the Review Assistant server process has pinned a few cores on our host server. The resolution has been to restart the service manually. I would characterize our complexity and volume of usage of Review Assistant to be low which leads me to believe the CPU utilization is not legitimate.

Are there any known triggers for valid sustained CPU utilization or known issues of the Review Assistant server process? What details I can capture to provide better information?

We encounter the same problem. We will try to fix it in the next build, now we don't know how to reproduce it.
Just restart Review Assistant server, when you encounter the problem again.