Hello! Is there a way to schedule the Last Tuesday of the Month in the Cron scheduler on the UI? like 2L in the Day of the Week field?

Hi Prefect Team! I'm looking to disable cloud logging since our implementation will be routing our logs via k8s directly to splunk. I tried setting an env value of

PREFECT__CLOUD__SEND_FLOW_RUN_LOGS=False

in our global container config which I see being recognized by Prefect Cloud, however there are logs still populating for the run (see attached). Do I perhaps have the wrong value defined or could I be missing something?

Hi I deployed prefect to my Kubernetes cluster using the Helm chart. It has been working for a while now. But I am now getting this error when visiting the UI:

TypeError: Cannot set properties of undefined (setting 'role')

Anyone know what this means?

Hi Prefect Team. I have a flow with tasks task1->task2->task3->task4. It is scheduled to run everyday and the flow runs just fine. But I want to use the UI to do the below activities once in a while. Can you let me know if I can do the below activities? 1. Sometimes I want to run just one task. Is it possible to run task3 from the UI? If yes, then how do I do that? 2. Assume that task2 has failed. If I run the flow once again, all the tasks will run from the beginning. Can I re-run the flow from the UI by ensuring that the tasks will run only from the failed task? i.e task1 will be skipped because it was successfully completed last time. the flow will run from task2 onwards.

Hi. I am using prefect server 1.0. Flows and tasks have been running ok. But now they only show log entries for the very beginning and end. I.e. I lost the richness of all those logger.info I made. Logs do show up if I run locally. What have I done and how to fix?

Also on a separate topic, the need to know the slug in advance and to know what quirky append it has, e.g. “-1” or “-copy” is a problem when using create_flow_run and get task results. I think you have an old ticket for this but I lost a couple of hours on this yesterday. Also when to use startflowrun or create_flow_run is a confusing to me. I think is is in the wrong forum as it is not UI. I am new to slack. Can someone help move it?

Hi! How to get project name from running flow?

Hi! I've run into an issue with parameters set in Cloud UI. When I update existing parameters via UI it doesn't take effect immediately. As far as I understand the reason is that Prefect Cloud schedule 10 runs upfront. So right after parameters update I need to wait 10 runs before my changes will be applied. Or I need to change either something in a Flow's code, or in a Flow's schedule so Prefect Cloud will re-schedule this 10 runs with updated parameters. It seems very strange behaviour. Is there any way to force this "re-scheduling" after each update in parameters via UI? To be more precise. Let's say I've got such Flow:

import pendulum
from datetime import timedelta
from prefect import Parameter, task, Flow
from prefect.schedules import Schedule
from prefect.schedules.clocks import IntervalClock

schedule = Schedule(clocks=[IntervalClock(start_date=pendulum.datetime(2021, 9, 28, 8, 0, 0, tz="UTC"), interval=timedelta(minutes=10))])

params = {
    "message": "message version 1"
}

with Flow("test_changing_parameters_from_ui", schedule=schedule) as flow:
    p = Parameter("params", default=params)
    task(lambda x: print(x))(p["message"])

I register it in Prefect Cloud. And right after registration Prefect Cloud schedules 10 runs of my Flow. After that i change

message

in this Flow via Cloud UI. For example, set

"message": "message version 2"

. I expect that in the next run updated message will be printed for me. But in fact I need to wait for 10 more runs before i'll be able to see my "message version 2".

Hi. I have prefect server set up. I see the scheduled flows are submitted bu the agent never moves it to run state. Any idea why and what the fix could be?

Hey all! We are running Prefect/Apollo/Hasura/Prefect-Agent (v 0.14.16). on Kubernetes on EC2 in AWS We run our Prefect-Agents as Local, not as K8S Agents. We find that when a Pod dies and is recreated by K8S a new Agent is created, registered, and becomes visible in the UI; however, the Agent that was killed when the Pod died turns into a Zombie and never gets cleaned up until we manually hit the Clean button a couple of times. When the agent count gets very high the entire platform bogs down, and the UI has trouble rendering. I thought that Towel was a service to help with this kind of thing - is there something special we need to do to get this set up?

Hey all! I recently came across this page (https://orion-docs.prefect.io/concepts/task-runners/) that showed a way of using dask.annotation to set the priority of each task, but I can't get it to work. Since I couldn't import DaskTaskRunner for the life of me I tried using LocalDaskExecutor, but I'm not sure if it does the same thing:

@task
def file_write(x):
    print(x)
    with open('test_result.txt', 'a') as f:
        f.write(str(x))
    return x

with Flow("priority_test", executor=LocalDaskExecutor()) as flow:
    with dask.annotate(priority=-10):
        written1 = file_write(2)
    with dask.annotate(priority=0):
        written2 = file_write(1)
    with dask.annotate(priority=10):
        written3 = file_write(0)

I expected it to write "012", but am consistently getting "201"

Hi all! I’m using Prefect 2.0b and I am running it on my dev machine.. I want to access the Orion UI from another machine but it shows me no data because it’s making API calls to localhost:4200 instead of the API URL I set (using

PREFECT_API_URL

) to

0.0.0.0:4200/api

Is there another way to accomplish this?

I am on v1.2 and Core. If I used cli to register a flow from a python script to a remote server it seems to work (except it ignores the scheduler). But when I use flow.register from within the code it gives an error. Graphql validation fails unknown type “register_tasks_input”. Any idea what I am doing wrong?

Hi there, I have a large data set that I want to run. It’s taking a long time. I want to break down my dataset to smaller batches, and run each batch in parallel. Is there a good way to do it using Prefect workflow? Thank you!

Hi all! We are transitioning our python scripts and others from Heroku to Prefect. We have prefect cloud, but what is the best way to run a prefect agent with the needed dependencies for our python files. We were just using prefect docker agent start on the VM, and pointing our flows to a dockerfile with the correct dependencies. This was working but would always stop working after a few flow runs. Does anyone know of any source code for a good docker compose for prefect agents to run on a VM, or where we should look for this info? Thanks!!

Hi. Is Prefect team know that there is issue with Flow Logs and scrolling there. In Live mode it sometimes automatically scrolling up and down many times.

I am a beginner with Prefect, so I searched the internet and followed tutorials to see UI and server, during installation and configuration I ran the command "prefect server start" but I got a message of error, have you please on that? I have docker and docker compose install

Hi, folks, a work flow finished correctly but UI does not show anything.

Hi, team Prefect! Updated prefect-core to 1.2.0 version. The problem is that I don't see registered FLOWs in the UI

Hello , when I restarted my laptop, I tried to run Prefect on local, so I typed the command perefct server start, but an error showed me "prefect: command not found" do you have an idea?

Hey everyone! Everything seems to be setup correctly so far, but I get the error "Flow is not contained in this Storage". Even though, I can docker exec into the storage in question and execute the python file manually. I've written a more detailed description with the actual code in the GitHub discussion board https://github.com/PrefectHQ/prefect/discussions/5680 - but did not get any responses so far. Does anyone have any idea what I did wrong?

Hi all,

Is there a way to schedule on the dask executor and still use the Prefect Server GUI to see the flows ?

Hi all, It seems that in the orion-ui Run Time is not an average, as the "AVG" after the duration seems to indicate, but a sum of run times. Is this meant to be an average run time or a total run time?

I am wondering if there is a pattern that exists in prefect 2.0 to say that a Flow had nothing to do. My use case is that I have a Flow checking every 5min for files in the s3 bucket of a partner and when they are files I process them with a series of tasks. The dashboard is showing a lot of successful tasks. Would using a subflow be a good pattern there? One flow "checking" and one flow "processing" ? Maybe having a sub flow status "success nothing to do" would work. I also have another use case, in the same flow I am processing those files and 0.1% of the records are not "valid" I am logging them as warnings but wondering if there is a way to report on those "invalid" records, seems to be a pretty common use case

Is there a way to see the content of a flow I've registered to prefect cloud? To double check what version of it is up there Edit: IIRC the source code of the flow never gets uploaded, right? So I guess a better version of the question would be "can I see where the flow is stored so I can grab and unpickle it myself"

Hi, is it correct that setting the task name using task_run_name from prefect 1 does not exist yet in prefect 2?

Does anyone know if we should be able to click through a task run and see it's log? Currently it seems the log is only on the flow run level?

I'm not sure if this is the right channel, but I was wondering why Postgres 12 is not sufficient for Orion?

Perhaps my Google search skills aren't quite up to the task, but I'm trying to find the IP range that Prefect Cloud uses to communicate with other services. Right now, we were running into difficulties using the AirbyteConnectionTask without opening our AWS Security Group up to public access for the task to work which we aren't super excited about. I have the logs added in the thread, but in summary, it fails and shows the below stack trace when we only have port 22 open to a specific IP range and it succeeds when we open up the SG. Has anybody else run into this using the AirbyteConnectionTask?