Hi folks!
We are seeing some strange behavior as flows are getting queued up (with no other flows running). They remain in queued state until we reboot the machines the flows get executed on.
Further, we have older flows showing in queued state, without a parent flow, and there is no option to clear them out. See attached screenshot for clarity.
Two questions:
- Is there a way to clear these queued flows manually?
- Are these queued flows consuming unattended licenses in the environment?
Thanks!

Report
All responses (
Answers (