@Marvin If I have a tag defined on a flow deployment, can that be used to limit the concurrency on the tasks in any run created using that deployment?

Yes, you can use tags to limit the concurrency on the tasks in any run created using a deployment. Task concurrency limits use task tags. You can specify an optional concurrency limit as the maximum number of concurrent task runs in a Running state for tasks with a given tag. The specified concurrency limit applies to any task to which the tag is applied. If a task has multiple tags, it will run only if all tags have available concurrency. Tags without explicit limits are considered to have unlimited concurrency. Please note that if the concurrency limit is set to 0 for a tag, any attempt to run a task with that tag will be aborted instead of delayed. Task tag limits are checked whenever a task run attempts to enter a Running state. For more details, you can refer to the Prefect documentation here.

Do tasks inherit tags from deployments?

Yes, tasks do inherit tags from deployments. Tags set on a deployment will be inherited by that deployment's flow runs. These tags can then be used to filter what runs are displayed on the primary UI dashboard, allowing you to customize different views into your work. In addition, in Prefect Cloud you can easily find objects through searching by tag. For more details, you can refer to the Prefect documentation here.

This answer is incorrect.