Hello - in prefect 2.0, is there a way to provide the task name dynamically ? For example, if I have a function defined as a task which is being called multiple times from a flow, I want to append a dynamic suffix to the task name.

Hi, I have a question about the new pricing for the Prefect Cloud. It has increased from 450€/month to 1850€/month. But even with this high costs, there is a limitation of 10 automations. If a company is scaling and would like to switch from Free/Self Hosted to the Cloud is able to pay >22K/year for a workflow system, they should be able to automate all their workflows, because in a complex data environment only time based scheduling is not sufficient and you need more "When A has finished, run B" / "If B and C have finished, run D" etc. rules. How are you handling a logic like that, if only 10 automations are allowed even at this price point?

Hey everyone, I'm getting the following error Pydantic error (in thread) when a scheduled deployment runs. It looks like there's some issue with the way I've defined the schedule in

prefect.yaml

, but no change has been made to this and I have other scheduled deployments that are working fine with similar configuration. Has anyone run into this?

@Marvin What does this warning mean?

<frozen runpy>:128: RuntimeWarning: 'prefect.engine' found in sys.modules after import of package 'prefect', but prior to execution of 'prefect.engine'; this may result in unpredictable behaviour

in prefect 2.0 what is the best way to chain results between map tasks? Specifically, how should errors on specific iterations be handled if the remaining results are still desired? This seemed seemless in prefect 1.x but I am running into issues while migrating to 2.0

@Marvin does prefect3 requires a running prefect server ?

Hey all, I still am confused about the

work queue

and

work pool

behavior 🤔 I have created a deployment with work queue

wq1

. I have created a prefect agent with work queue

wq1

. •

Agent started! Looking for work from queue(s): wq1...

When I trigger a flow via API, it is shown as: • work pool:

default-agent-pool

• work queue:

wq1

However, the agent does not pick up that flow run 🤔 Any thoughts or suggestions? PS: I did it similarly before and it worked before, I think. PPS: I redeployed the flow already several times (i.e. whenever I needed to restart the related EC2 instance).

Hi, with Prefect 2.0, how to use command line to run a flow with parameters (prefect deployment run id ......etc)

Logs not visible on UI , how to fix this ?

Hi Team, I'm running into ECS permission issues while trying to deploy a flow-- Though I'm specifying ecs cluster on agent start, I'm getting a permission error on resource *. This user only has permissions to the ECS cluster listed. Any thoughts? Thanks.

prefect agent ecs start --cluster my-cluster-arn --launch-type EC2

botocore.errorfactory.AccessDeniedException: An error occurred (AccessDeniedException) when calling the RegisterTaskDefinition operation: User: arn:aws:iam::**********:user/********* is not authorized to perform: ecs:RegisterTaskDefinition on resource: *