Hello Team, we're following the instructions here to replace the deprecated

Deployment.build_from_flow

with

flow.deploy

. Previously we were using

path

parameter in

Deployment

class which indicates the path to the working directory for the workflow, relative to remote storage or, if stored on a local filesystem, an absolute path. However, there seems no equivalent parameter in the

flow.deploy

, as the only way seems to be using

flow.from_source (source = ..., entrypoint = ...).deploy(...)

. We wanna use an absolute path for local development since it's stored on a local filesystem, instead of pulling from the repo every time. Are there any way to do that?

Hi, when a worker gets killed or crashes while it is executing a flow run, the flow run gets stuck in

running

state. As this is confusing and inconsistent, I'd like to resolve it and get consistent states on our self-hosted Prefect server. I was hoping that a migration from agents to workers would fix it, but despite the worker's heartbeat functionality and workers being recognised as unhealthy/dead by the server, the flow run still remains in

running

. I can work around this by updating flows manually from external processes (e.g. k8s lifecycle hooks on pods), but I would like to avoid having to manage flow state from outside of Prefect itself. I'd be curious to learn how others are approaching this issue. Maybe I'm also still missing something on Prefect, my expectation was that it would mark flow runs from dead workers as

failed

.

Hi Team! We've configured SCIM for Azure AD groups, but some members are not synchronized. The Azure AD provision log states: "The state of the entry in both the source and target systems already match. No change to the user <email> currently needs to be made. SkipReason: RedundantExport." So it seems that the user is present in Prefect (in fact one of the users got an e-mail invite, but can't log in), but not visible in the Prefect admin UI. Any suggestions?

@Marvin Getting the error with pydantic 2, but pydantic 1 is ok:

pydantic.errors.PydanticUserError: If you use `@root_validator` with pre=False (the default) you MUST specify `skip_on_failure=True`. Note that `@root_validator` is deprecated and should be replaced with `@model_validator`.

Hi, is there any possibility to download task logs?

Hi Team, can anyone please help me with the significance of this error

06:55:16.136 | ERROR   | prefect.infrastructure.process - Process '<function uuid4 at 0x7fe62066ab80>' exited with status code: -9; This indicates that the process exited due to a SIGKILL signal. Typically, this is either caused by manual cancellation or high memory usage causing the operating system to terminate the process.

Hi all, doing some research and was curious had anyone used MS SQL server with Prefect before?

S3StorageBlock is not working with Minio as we cannot specify the endpoint_url. This is something I added on the collection-aws. Will this block move to the collection-aws ? If not, how can I do a push request to the branch ?

Hi All, figured I'd ask here in case anyone has experience with this. We are deploying ECR containers that have all of our flows using github actions, however the github action fails running the

aws-actions/configure-aws-credentials

action with

Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers

. Has anyone seen this error before when trying to package their flows into a container?

Hi everyone! I just downloaded Prefect 2.0 and was wondering if it's possible to create a dependency between two different flows. The reason I'm asking is because I want each flow to run in a different conda environment so it needs to be on its own deployment, but I also want it to be possible for a flow to run depending on the state of another flow in a different environment. Any help would be really appreciated. Thanks!