Short answer: those warnings are expected today whenever a task has tags but no concurrency limits exist for those tags. There isn’t a built‑in switch to disable the acquisition attempt or that specific warning. It’s a known noise point we’re tracking: issue #19250. Ways to avoid the warning without removing your tags: - Suppress just the concurrency logger via a logging config (recommended) - Or, define a high concurrency limit for those tags (works, but still does concurrency bookkeeping you don’t need) Option 1 — suppress via logging config 1) Create a logging.yml and lower the concurrency loggers to ERROR so the WARN doesn’t show:

version: 1
disable_existing_loggers: false

loggers:
  prefect.concurrency:
    level: ERROR
    propagate: true
  prefect.concurrency.v1:
    level: ERROR
    propagate: true
  prefect.concurrency.v1.services:
    level: ERROR
    propagate: true

2) Point Prefect at this file: - Set env var before you run:

PREFECT_LOGGING_SETTINGS_PATH=/path/to/logging.yml

- Or put the file at

~/.prefect/logging.yml

Docs: Logging customization Option 2 — set logger level programmatically at startup

import logging

for name in [
    "prefect.concurrency",
    "prefect.concurrency.v1",
    "prefect.concurrency.v1.services",
]:
    logging.getLogger(name).setLevel(logging.ERROR)

Option 3 — create a no‑op concurrency limit If you’d rather remove the warning by satisfying the check, you can create a limit with a very high value so it never actually throttles. This is heavier than Option 1 since it still acquires/renews leases. Docs: Tag-based concurrency limits If you want, I can share a minimal ready‑to‑drop logging.yml tailored to your setup.