Is there anyway to stop a run if a task doesn't find any data but without it failing the run? I found the following code at https://discourse.prefect.io/t/how-can-i-stop-the-task-run-based-on-a-custom-logic/83 but I'd like it to just say "skipped" instead of it showing as a failure.

from prefect import task

@task

def signal_task(message):

if message == 'stop_immediately!':

raise RuntimeError(message='Got a signal to end the task run!')

Hi, in a flow with subflows, if a subflow fails at a task and I retry the parent flow. the parent flow creates a new subflow run and starts all the tasks in it(completed or otherwise). I was expecting it to run the same subflow and continue with the failed task. Am I not understanding the logic or am I missing a settings somewhere?

Is there any way to actually rename a flow run in Prefect 2 with

@flow(flow_run_name="foobar")

? Even the examples from the docs copied verbatim do not work (see replies).

Hi, I have a pipeline in AWS where things trigger each other and would like to move it entirely to prefect but have some doubts/questions: 1. There is a Lambda_1 triggered on a schedule via cron job in Eventbridge. At the end this Lambda_1 has some python code to trigger Lambda_2 a. Q1.1) Can I trigger Lambda_1 in a Prefect deployment? b. Q1.2) Can Lamba_2 be triggered as well from Prefect depending on the completion status of Lambda_1? 2. There is a Lambda_2 that at the end of its python code does the following: updates the Fargate service for Container_1 to desired count = 1 (basically starts a task that wil be billed starting then). a. Q2.1) Can I update, with Prefect, the service for Container_1 to have 1 task running, depending on the completion status of Lambda_2? b. Q2.2) Can I start, with Prefect, the Prefect deployment for Container_1 depending on the completion status of the service update? c. Q2.3) Can I, with Prefect, update the service again to 0 so that it stops the billing? this should also depend on the completion status. If all python code was succesfull then stop and if not then retry a couple of times the flow for the deployment in Container_1 3. The Container_1 has a Prefect deployment that at the end calls Lambda_3 and Lambda_4 4. Lambda_3 is similar to Lambda_4 and it starts updates another fargate service to have 1 task running. Then it should start the Prefect deployment inside Container_2 5. Container_2 is similar to Container_1. It should call another lambda if the python code run succesfully and should retry a couple of times if there was any errors. At the moment I have all these triggers/calls within the codes and have to no proper way to see unified logs for everything so I thought Prefect could help and simplify my experience. General suggestions on the overall architecture are also welcome :)Thanks!

Hi all I'm getting a

Server error '500 Internal Server Error' for url

in an orchestration flow (run in Prefect Cloud) that is triggering many

run_deployment

calls. Is this likely an API limit being tripped?

Hi guys, I have a task querying a Redshift database whose credentials are set outside the task. I use a docker storage and ecs run. Locally the flow runs fine, on the ecs it times out connection to redshift cluster. If I remove the task decorator the database is queried fine. I think only database credentials are not passed because loading to s3 works so its not aws credentials. Has this to do with mapping in tasks?

What is the difference between flow.set_dependency and flow.add_edge in Prefect 1.0?

How would you describe Prefect in a compact way that highlights its features? It's not a workflow manager in the sense that it is not Camunda, it is not Temporal, it is not AWS Step. It's not Conductor by Netflix

Hello! I’m curious if in Prefect Server UI you can unarchive a flow? This would be the use case, I have multiple versions of the flow, the latest one is running, but I find there is a bug and I want to roll-back to the previous version. I know I can delete the latest version, but that doesn’t make the now latest version unarchived. Thank you!

Hey all! Running into an issue with our prefect deployments that I am wondering if anyone else has seen or has any thoughts on. We have a large quantity of flows that are running/queued, but each flow itself should not take very long. For some reason a large number of these flows are entering a running state and then never exit that state. The associated Job deployment for those flows gets cleaned up, but the flow itself still exists as running and is blocking the queue