yes, we have the old agent work pool and new worker work pool running on the same kubernetes namespace, with the same work queue name, and now that you mentioned it everything makes sense, thank you. the agent was "stealing" the flow runs from the worker and causing the issues. why though not sure, since although the work queue name is the same, the pools are separate.