Hi friends, I set up Prefect on an Openshift platform, I can see all pods are up and running. Prefect UI and graphql endpoint comes up. But when I try to add projects , its not doing anything and getting an error on console. What should be the problem ? This is my test env, https://prefectuiroute-e11dbf-dev.apps.klab.devops.gov.bc.ca/ - Any clue?

Hi folks, in a prefect flow , for one particular task, I am trying to raise a SKIP signal

from prefect.engine.signals import SKIP
........
........
raise SKIP('Skipping all downstream dependencies.')

With this all the following tasks are being skipped and was expecting the flow state will be

skipped

. Though the following tasks are being skipped but at the end the flow becomes

successful

. I have two questions around : 1. Is this something expected? 2. If this is expected, whats the remedy . Do I need to explicitly use a state handler on top of it to make the flow

skipped

eventually

Hi all. I'm trying to set up a Prefect docker agent as a systemd service (CentOS). What is the recommended practice for storing the prefect API Key and passing it on to the systemd service?

super basic question but how do I access the result of a mapped task from the

state = flow.run()

object? I always get a

KeyError

when trying to do

state.result[mapped_task].result

but

state.result[not_mapped_task].result

works fine

Hello Prefect Land! Simple request. I have a notification (new file upload) set up in AWS S3 that goes to SNS. From there, it branches to send an e-mail and also kick off a lambda function that kicks off a flow in Prefect. When I receive the e-mail, I can see the entire file path in S3. How can I get that same info over to my Prefect flow so I can parameterize? I hope I’m making sense… Best All!

Hi I tried to run the prefect server on my ec2 instance, I modified the security group so that it accepts the inbound rule to accept port 8080, but i could not able to access the prefect ui from my laptop, do you have any idea where I need to work on? fyi the grapql url with port number 4200 is accessible but just not 8080 of UI

@Marvin I'm trying to setup a notification system in Prefect 3.2.8 using a custom webhook block. The block has a Webhook URL (let's say myurl/notify) where I accept POST requests like myurl/notify?run_id:x and I've set into the block the field Query Params {"run_id":"{{ flow_run.id }}"} however, when sending the notification I get the following error: 095750.753 | WARNING | prefect.server.events.actions - Action failed: 'The notification block was invalid: KeyError("params/Placeholder(full_match=\'{{ flow_run.id }}\', name=\'flow_run.id\', type=<PlaceholderType.STANDARD: \'standard\'>)")'

hello! i use aws lambda to create a flow_run using prefect sdk. i started getting the opentelemetry related error after i upgraded to prefect3. does anyone have any insights?

@Marvin I have a deployment created that is set to run on an active work pool. The work pool seems healthy, but all of my auto-scheduled runs are late and I cannot get them to run at all, since they are stuck in the Late state. Can you help with this?

Hi guys, I am wondering something about prefect 3.0 and I am curious about how community is developing flows right now. As it is said in the official doc "Prefect future objects must be resolved explicitly before returning from a flow". That means that every task must be resolved during the flow execution. In prefect 2.0, all tasks were automatically waited. In fact, the flow returned a list of tasks states. Right now, how are you developing your flows? 1. Do not use

.submit

for the terminal futures? 2. Use

.wait()

for terminal futures, and return a list of tasks states manually? 3. Use the

wait

utilities to resolve terminal futures?