Hello, I am setting PG db for orion. I don't have super user rights on db. I am able to create tables but creating extensions is problem. How can I know what extensions orion will require and is there anything else while setup which require SU right and outside of normal schema objects? Thanks

in 1.x, is it possible to get the labels of the flow run? I want to create sub-flows with the same labels, but can’t find a way to dynamically get the parent flow run’s labels to pass to the sub-flow.

Just curious, any plans to support Webhook notifications via... MS Teams 😅?

Hi! I have a Prefect flow that runs successfully and returns a

Flow Run Succeeded

but the process doesn’t exit after success and instead hangs. Any idea what’s happening?

Hey all, so I’m using the Kubernetes Agent to run flows and I was wondering what if any support there is for defining some kind of DAG like workflow where parallel tasks can run in separate pods? Is that something that Prefect can do with the kube agent? Feel free to RTFM me if I missed something critical in the docs, just not finding anything myself

Hi Community, In Prefect Cloud 1.0, is it possible to replace the current version of the flow when publishing? The reason I ask is that I made a few changes to my code that can resolve the failed task. But when republishing the revised flow, Prefect creates a new version of the flow, meaning I can't restart the failed task but reruning the whole flow. thank you.

Hey all, just getting back around to re-working my migration project from Prefect 1x to 2x. Hitting an issue when trying to register a SqlAlchemy Configuration Block: https://github.com/PrefectHQ/prefect-sqlalchemy/issues/28

Hello Prefect community! Wondering if it's possible to have a custom flow run name for the scheduled flow? Alternatively, is there any way #prefect-ui for the UI to show which deployment the scheduled flow is associated with?

Hi All, I am using prefect CLI to login the prefect cloud by using

$ prefect cloud login --key xxx_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

But i get the following error

Unable to authenticate with Prefect Cloud. Please ensure your credentials are correct.

My env is pipenv. And I am using prefect 2.2.0

$ prefect --version
2.2.0

And I have created the API Key here

Hey folks! I'm trying to figure out how to best deploy a Prefect Agent on our kubernetes cluster along with our JupyterHub, and can't really seem to find any resources on just deploying the agent 😞 Any pointers?

Also I notice https://docs.prefect.io/tutorials/kubernetes-flow-runner/ comes up in Google Search if I try 'Kubernetes Prefect 2.0' but it's a 404

I'm generally pretty confused - I have a k8s server, and I want to hook that up to prefect cloud. And I can't seem to find how. Would appreciate any help / pointers, particularly if I can do so via helm

Hey all, new to prefect ^_^ I’m trying to make use of the github block - does anyone know where i can find documentation on this? (more specifically, how i can go from the block being set up in the UI to referencing this within a task)

Hello, I've tried the new 2.X version of prefect and it works with my scripts migrated. but as I have a lot of scripts in a machine already I'd like to do the migration the smoothest way. Could I have in the same machine prefect0.15 and 2.0 in differents virtual environments? thanks

Hi, is there a way to set a timeout for the K8s jobs executing the Flow Runs? I'm using 1.xx

Hello. I’m using ECS Agent and dask executor using fargate cluster to parralize multiple ML model training. When I use dask executor, flow as ECS Task use DescribeTask API to dask scheduler so many time. CloudTrail show API call from Prefect ECS Task as 500/minute. So API call throttling error occur many times. Is there any way to reduce using DescribeTask API call when I use dask executor?

hello. I am using sqlalcemy with prefect2.0. However, I am in trouble because the log appears twice. (from prefect, and, from sqlalcemy) Do you know any solution? thank you,

Hello Prefect engineers. Experiencing what might be a regression bug from the new 2.3.0 release. This error does not occur in Prefect 2.2.0. Nothing about the flow or deployment was changed between the Prefect update. Unfortunately, I am unable to create a minimally reproducible example without revealing our company code...but happy to share it with a Prefect engineer over a call. Thanks in advance! However, been using the new arguments for deployments in our CICD pipeline and it's been working great 🙏

hi, we have a number of tenants on Prefect 1.0, do we have to explicitly ask for them to be enabled on Prefect 2.0? I couldn't see any docs about this, are tenants now workspaces?

Hello team! I am Joseph and new to prefect, which material can I use to get start please?

Hi Team, Sometimes we are seeing task failures in ECS with this error

Failed to start task for flow run ad860ca0-61df-4055-b3f6-7f48c2d9ead4. Failures: [{'arn': 'arn:aws:ecs:us-east-1:XXXXXXXXXXXX:container-instance/XXXXXXXXXXXX', 'reason': 'RESOURCE:CPU'}, {'arn': 'arn:aws:ecs:us-east-1:XXXXXXXXXXXX:container-instance/XXXXXXXXXXXX', 'reason': 'RESOURCE:MEMORY'}, {'arn': 'arn:aws:ecs:us-east-1:XXXXXXXXXXXX:container-instance/XXXXXXXXXXXX', 'reason': 'RESOURCE:MEMORY'}]

Understandably, its because enough resources are not available on ECS nodes to schedule the tasks when launch type is EC2. But as per my understanding, in such cases the ECS task should get scheduled with "Provisioning" state, and ECS cluster should scale out and add more instances after which the task would run. However in our case we see above error and the task just fails to schedule. Is there a specific parameter we are missing which will provide the ECS feature that i mentioned above ? or this is the expected pattern ?

Hi there, did anyone get a Docker infrastructure with a private Docker registry in 2.3.0 to work? I defined a "Docker Registry" and a "Docker Container" block and used the Docker Container block as infrastructure block in the deployment.

prefect deployment build myflow.py:myflow \
--path /prefect/flows/myflow \
-ib docker-container/dev-image \
--name local_docker \
--skip-upload \
--apply

After running the deployment it breaks with "no basic auth credentials". Inspecting the "Docker Container" block shows that it should use the defined registry block. Double checked the credentials multiple times and successfully logged in with

docker login...

I tried the same on 2.2.0 with the same error after executing the deployment :-(

set the channel topic: Welcome! 👋 -Please put code & tracebacks in 🧵 -✅ means addressed, not always resolved -G bugs & feature requests : https://github.com/PrefectHQ/prefect/issues -Discourse: https://discourse.prefect.io

Is there planned to be any concept of "agents" in the api/UI that shows the different agents that have been connected over time, when they were last active, etc?

Hi There, I just started with Prefect v2, and trying to figure out the following: 1. Let’s assume we deployed a new pipeline to Prefect Server, and this new pipeline has new dependencies (external python libraries), How we can automate the installation of these dependencies on the agent execution environment while guaranteeing high availability (assuming that pipelines are running 24/7 on our servers)? 2. In the case of an Agent deployed on Kubernetes, How does the agent mange the workload across the Pods, is it automatically handled by the Agent, or do we need to handle this from our side?

Is there any way to change the timezone on the UI in 2.0?

Is it possible to run tasks in docker environment? Usecase: I have a Flow composed of 3 tasks. First two are pretty simple, and can be done without using any external python library. The third one requires some external python libraries and a few system dependencies to be installed. Is there a way to run the first two tasks on the host environment, and the third in docker?

Hi everyone - we're still on Prefect V1 for Q3. We had a failing heartbeat with a long-running API backfill. I did switch our configuration to 'threads' as documented here, but two backfills failed again last night (while a third smaller one succeeded). What's interesting is that the ECS Cluster is still active but the agent has stopped responding to new incoming requests, and there's likely a zombie job in Prefect due to this. The specific question I have is "Has anyone else had a problem of a new FARGATE job stopping the agent itself from responding?" I thought, based on the configuration, that those would have been on separate FARGATE clusters on ECS.

Hey all, we’re hosting @Will Raphaelson, a senior tech product manager at Prefect, on PrefectLive today at 3p Eastern where he’s going to show the latest improvements to deployments, in particular using Docker and Github! Come join us live on Twitch!