I am using PREFECT_LOGGING_EXTRA_LOGGERS to set an extra logger from one of my libraries to show up in my flow logs. I want to set the log level of that extra logger. mylib's logger has level set to DEBUG because that is needed by one of the two handlers mylib.logger's FileHandler has level set to DEBUG mylib.logger's RichHandler has level set to INFO I want the output of the logger in PrefectUI to also be INFO but I'm not sure how to set that. I'm currently seeing all the DEBUG messages, which is too much

Hello Prefect community, how can I retry a task on specific error codes (500) with the same inputs but using conditional logic based on the number of retries. So if the previous error code was 500 and the current retry count is 2, follow this particular path, otherwise follow the standard path? Our OCR pipeline has a long running task that often returns 500 if the file cannot be read. When we receive this error, we want to do postprocessing on the pdf (converting to an image) and rerun the task.

@Marvin How do I pass a event payload as a trigger parameter for a deployment?

Hi All, General Question - Can we deploy prefect on open shift ? Is there a doc for this ? Appreciate your help!

Hi all, I am seeing the following errors in my self-hosted prefect server when under load. How concerned should I be?

13:15:55.415 | WARNING | prefect.server.services.failexpiredpauses - FailExpiredPauses took 29.592499 seconds to run, which is longer than its loop interval of 5.0 seconds.
13:15:55.444 | WARNING | prefect.server.services.flowrunnotifications - FlowRunNotifications took 29.644721 seconds to run, which is longer than its loop interval of 4 seconds.
13:16:28.024 | WARNING | prefect.server.services.failexpiredpauses - FailExpiredPauses took 6.629446 seconds to run, which is longer than its loop interval of 5.0 seconds.
13:16:28.037 | WARNING | prefect.server.services.marklateruns - MarkLateRuns took 6.655057 seconds to run, which is longer than its loop interval of 5.0 seconds.
13:16:28.039 | WARNING | prefect.server.services.recentdeploymentsscheduler - RecentDeploymentsScheduler took 6.648737 seconds to run, which is longer than its loop interval of 5 seconds.
13:16:42.554 | WARNING | prefect.server.services.recentdeploymentsscheduler - RecentDeploymentsScheduler took 5.717242 seconds to run, which is longer than its loop interval of 5 seconds.
13:16:42.569 | WARNING | prefect.server.services.flowrunnotifications - FlowRunNotifications took 5.730481 seconds to run, which is longer than its loop interval of 4 seconds.
13:16:42.573 | WARNING | prefect.server.services.failexpiredpauses - FailExpiredPauses took 5.735392 seconds to run, which is longer than its loop interval of 5.0 seconds.
13:16:42.613 | WARNING | prefect.server.services.marklateruns - MarkLateRuns took 5.777756 seconds to run, which is longer than its loop interval of 5.0 seconds.
13:17:10.327 | WARNING | prefect.server.services.flowrunnotifications - FlowRunNotifications took 19.093586 seconds to run, which is longer than its loop interval of 4 seconds

@Marvin why would a server fail to start with this error:

sqlalchemy.exc.DBAPIError: (sqlalchemy.dialects.postgresql.asyncpg.Error) <class 'asyncpg.exceptions.DeadlockDetectedError'>: deadlock detected

Hey guys, I would like to instrument my self hosted Prefect deployment with

OpenTelemetry

(Its the last part of our micro-service architecture thats missing it) I was looking online and only managed to find a single old thread and one attempt that doesn't look working/maintained. Anyone tried this? Know if its doable even? • It would require passing the Open Telemetry trace id from a parent flow to each of its subflows/tasks. Prefect run context which might be an option for this does not appear to allow additional fields. • The tasks/flows themselves would also need to be instrumented of course Would appreciate any help 🙏 Thanks all

New to using Prefect...there's gotta be something I'm missing in setting up. Deployed in GCP, using Prefect CLI and dbt and BigQuery. Just trying to write a simple flow for testing. I used the server UI to save a block for the link to my test dbt repo. The repo is public. I'm trying to reference that block in my flow, and I just keep getting an error that the project_dir path is invalid.

Hey guys, do you know of any good available projects that I can take a look at that use FastAPI with Prefect (and dask scheduler behind it)? bonus for using mlflow as well

@Marvin is it possible to set nodeSelector and tolerants on a work pool so that all flows described in my prefect.yaml that are associated with that work pool will be scheduled on a specified node pool?