My mistake. I accidentally shared the “Dev” version on the Workload Usage specific graph. Thank you for pointing that out.
I wish the situation were as simple as you mentioned, but unfortunately, it’s not. Here’s the graph for the “live” version.
As you can see, 98.6% of it is from Fetching Data processes. Not from a scheduled workflow.
Scheduled Workflows, on the other hand, consume far less WU.
My recursive workflow simply makes a basic API call. It’s unrelated to my current data, so it’s definitely not running 600,000 times, @georgecollier.
And here, take a look. It’s still consuming a substantial amount of WU.
When I looked into what’s consuming all this WU, I arrived at the following graph:
These graphs are from the “Screen Analytics” reusable element.
However, this reusable element is nowhere to be found because I removed it last night. Yet, it’s still consuming a significant amount of WU.
Do you still thought it’s a recursive workflow? Is your money still on it? @adamhholmes