We are currently experiencing very high CPU usage on a server caused by the workflow manager backend and associated services. The CPU is constantly locked at 98-99%. We believe this to be caused by some rogue workflow in the environment as we can't seem to find any configuration issues. My question is, is there a way to utilize the ControlPoint workflow analysis tool to narrow down any workflows consuming high resources? Like potentially logging to workflow history a lot in some stuck loop? We have a SharePoint 2013 on premise environment that contains hundreds of workflows so it's very difficult for us to comb through running instances to see what could potentially be causing this. It doesn't appear to be a resource issue because the services immediately consume all available CPU once we add more cores/frequency.