We created a deployment:

<https://app.prefect.cloud/account/400***/workspace/8d8***/deployment/2f5***>

- it has the

staging

tag. We have a running agent:

$ /usr/bin/python3 /usr/local/bin/prefect agent start 360***
Starting agent connected to 
<https://api.prefect.cloud/api/accounts/400***/workspaces/8d8***>...
  ___ ___ ___ ___ ___ ___ _____     _   ___ ___ _  _ _____
 | _ \ _ \ __| __| __/ __|_   _|   /_\ / __| __| \| |_   _|
 |  _/   / _|| _|| _| (__  | |    / _ \ (_ | _|| .` | | |
 |_| |_|_\___|_| |___\___| |_|   /_/ \_\___|___|_|\_| |_|
Agent started! Looking for work from queue 
'360***'...

The work queue also has the tag

staging

. When I click on "Run" in the Cloud UI in the deployment, it is scheduled but the flow run has no tags assigned. And I guest this is the reason why it is never picked up by the agent. Or how can I debug this issue?

Hi Tim 🙂 You have identified a UI bug that we should have fixed by the next release. (That in the flow run details, a deployment’s tags are not shown.) However, the UI bug should not affect the work-queue’s ability to identify a deployment with the right tags. It is a UI issue. That being said… The tag matching for deployment-worqueues is AND not OR based which means that you need to ensure that the work-queue lists ALL the tags that your deployment has.

Thanks for the information! Both, so the queue and the deployment only have the

staging

tag and nothing else.

What version of prefect are you using?

2.0.1. We just upgraded to 2.0.2 but can only test the new version later. I will try out both, so upgrading to 2.0.2 and the new command. I will report back if it worked. Thanks!

try the new command

Thanks, this worked!