@<1523701070390366208:profile|CostlyOstrich36> any thoughts?

• Yes, in this scenario both the Agent & the code were present in the same machine
• The queue being assigned to default was something we had changed after some debugging, yes.
• We verified from the ClearML UI that the queue that the task is being assigned to wasn't default.
• The pipeline only worked through remote execution when the entrypoint script was in the root of the git repo (which kept getting picked up as the working directory)

Hi @<1523701132025663488:profile|SlimyElephant79> , are you running both from the same machine? Can you share the execution tab of both pipeline controllers?

Also, reason that they in queued state is because no worker is picking them up. You can control the queue to which every step is pushed and I think by default they are sent to the 'default' queue