< Marvin> Can you provide help with this error ```uv run pre Prefect Community #ask-marvin

<@ULVA73B9P> Can you provide help with this error...

Santiago Gutierrez

06/10/2026, 11:05 PM

@Marvin Can you provide help with this error:

Copy code

uv run prefect worker start -p my_pool -q eds_high
╭─ Error ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ Unused Tokens: ['eds_high'].

My queue is registered already:

Copy code

$ uv run prefect work-queue ls
                                     Work Queues
┏━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━┓
┃ Name     ┃ Pool        ┃                                   ID ┃ Concurrency Limit ┃
┡━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━┩
│ eds_high │ my_pool  │ ecbe917e-dfd0-4481-b30c-87034218edb6 │ None              │

Copy code

$ uv run prefect work-queue inspect 'eds_high'
WorkQueue(
    id='ecbe917e-dfd0-4481-b30c-87034218edb6',
    created=DateTime(2026, 6, 10, 22, 51, 25, 551871, tzinfo=Timezone('UTC')),
    updated=DateTime(2026, 6, 10, 22, 51, 25, 551892, tzinfo=Timezone('UTC')),
    name='eds_high',
    priority=2,
    work_pool_name='my_pool',
    work_pool_id=UUID('f82c77c0-5b04-4735-955e-c1e008df4aad'),
    status=WorkQueueStatus.NOT_READY
)

Marvin

06/10/2026, 11:05 PM

✅ thought for 101.9 seconds

Marvin

06/10/2026, 11:06 PM

Yes —

-q

is the right flag in Prefect 3.x, and your command looks valid:

Copy code

bash
uv run prefect worker start -p my_pool -q eds_high

I verified the CLI help for

prefect worker start

, and it includes:

Copy code

text
--pool       -p   TEXT   The work pool the started worker should poll.
--work-queue -q   TEXT   One or more work queue names for the worker to pull from.

So the error is not because

-q

is unsupported. What’s likely happening The message:

Copy code

text
Unused Tokens: ['eds_high']

usually means the CLI parser did not treat

-q

as taking a value in the way it expected. A few likely causes: 1. CLI/version mismatch You may be running a Prefect version where the installed CLI behavior doesn’t match current docs/help. Check your version:

Copy code

bash
   uv run prefect version

2. Try the long-form flag Sometimes this avoids parsing oddities:

Copy code

bash
   uv run prefect worker start --pool my_pool --work-queue eds_high

3. Quote the queue name just in case

Copy code

bash
   uv run prefect worker start --pool my_pool --work-queue "eds_high"

4. If you omit
-q
, the worker will poll all queues in the pool Since

eds_high

is already in

my_pool

, this may be enough:

Copy code

bash
   uv run prefect worker start -p my_pool

One important thing from your output Your queue shows:

Copy code

text
status=WorkQueueStatus.NOT_READY

That can indicate the queue/pool isn’t ready for work yet, which is separate from the CLI parsing problem. The worker should generally attach to a valid work pool, but if the pool is misconfigured, you may hit additional issues after startup. Recommended next steps Run these and compare:

Copy code

bash
uv run prefect version
uv run prefect worker start --pool my_pool
uv run prefect worker start --pool my_pool --work-queue "eds_high"

If the long-form command still fails, please paste: -

uv run prefect version

uv run prefect worker start --help

- the exact output of:

Copy code

bash
  uv run prefect work-pool inspect my_pool

and I can help narrow it down further. Relevant docs: - Work pools and workers - Deployment guides

2 Views

Open in Slack

Previous Next