I have an

@asset

that queries an endpoint when materializing. This endpoint has a concurrency limit of

n

, which means I need to only materialize

n

assets concurrently. I’ve setup the

QueuedRunCoordinator

with

tag_concurrency_limits

, say

http/limit: n

which limits to

n

. How do I apply this tag to my

@asset

? I’ve tried using

op_tags

but that doesn’t seem to apply it when materializing; and for backfilling, I’ve found that: • in the simple popup in the UI, I can specify a range, but I cannot specify this tag • in the “shift-click” popup, I cannot specify a range, but can specify the tag • on the command line, I can do both, i.e.:

--from x --to y --tags n

But at the end of the day, I always want this tag to be applied when materializing this asset. Is this possible?

Hey @Philippe Laflamme - what you've discovered is the current best way to do this. However, I agree with you that it's incomplete. Here's an issue where we're tracking adding this capability: https://github.com/dagster-io/dagster/issues/8979