How do you trace a runaway workflow?

[QIRO]

I have a workflow that has, as of two days ago, gone rogue and is consuming vast quantities of WUs.

I can see the workflow, but I cannot see what’s triggering it so often. I put guardrails up to prevent the process running more often than desired, but it’s still going, which may mean something else is triggering it.

Zooming into the log just presents a blank screen. How do you trace what’s trigging a backend workflow?

[johnny]

I would look at the different places you use the workflow at

And then in the logs just see where that backend workflow is being triggered at.

[QIRO]

I have managed to put a lid on it now, but I’ve still no idea why it was steaming off down the tracks on its own. The logs were no help, they show the workflow, but not what calls it.

Thanks for your help!

[ruiz86]

You can use the App Search Tool and looks for the workflows triggering the backend workflow.

If you have an external application calling your backend workflow, it will be harder to track.