I really enjoyed the file-less workflow of uploading flows to the Prefect 1.0 server and having them execute in the k8s infrastructure (via the agent, as k8s jobs). It seems it’s not possible anymore with Orion, is it? I don’t fully understand the benefits of the json/yaml files as opposed to the former API. Should I really embrace calling CLI and dealing with files as it is a superior approach? One obstacle in my workflow is I’m doing interactive work in a Jupyter kernel, running in the cluster, so getting a shell at the same host is not straightforward

Is there a public roadmap for future Prefect development and features?

Hi guys, I'm just getting started with prefect 2.0 in docker. I mounted file into /flows folder - but unfortunately I can't see it in the flows section in the UI... what am I missing?

root@24dc674d1f7d:/flows# cat flow1.py

from prefect import flow

@flow
def my_favorite_function():
    print("What is your favorite number?")
    return 42

print(my_favorite_function())

Hi community, Lately we have noticed the following error that occasionally caused failure for multiple unrelated flows (here is log example for one):

14:25:23 INFO Submitted for execution: Job prefect-job-2444a873
14:25:49 ERROR Failed to load and execute flow run: ConnectionError(MaxRetryError("HTTPSConnectionPool(host='<http://www.scorpiotankers.com|www.scorpiotankers.com>', port=443): Max retries exceeded with url: /our-fleet/ (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7efdbc010d00>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))"))
14:26:00 INFO Beginning Flow run for 'Destination Predict'
14:26:00 DEBUG Using executor type LocalDaskExecutor
14:26:00 INFO Flow run has already finished.
14:26:32 ERROR k8s-infra Pod prefect-job-2444a873-8887r failed.
	Container 'flow' state: terminated
		Exit Code:: 1
		Reason: Error

The specific error seems to reflect code from another unrelated flow. Any idea how one flow can throw an error in several other completely unrelated flows? before even the flow starts?

Hi, happy 2.0 GA 🎉 What is your opinion on how to structure Prefect 2.0 code within an organization? One big mono-repo? One repo per Flow? One repo per business value stream? Would love to hear your experience and perspectives! 😛refect-duck:

I've spent a few days trying to get accustomed to 2.0 after running 1.0 for over a year and a half. It looks amazing so far! However, there are two things I'm still trying to wrap my head around: Docker containers and storage. I've been trying to learn as much as I can from the documentation and this slack workspace but it's still a bit unclear. Previously, we have been building each flow as its own docker container and we have never specified any sort of local/remote storage beyond setting flow.storage to Docker. I suppose this is no longer supported in 2.0? The impression I'm getting from reading the documentation and slack is that people generally build a few base images, upload it to their container registry (Azure, in our case) and then store the flow .py files themselves in a remote storage location. Is this correct? If so, since I'm using Azure, can I even move forward with the migration right now or do I have to wait for blob storage support? In case it makes a difference, we run our agents in VMs and we're primarily using the cloud versions of the web service, other than for local development.

What I really liked about Prefect 1.0 was the

log_to_stdout

Parameter which automatically logs all print statements. Is there something similar for Prefect 2?

Is the Prefect 2.0 sign up page broken?

Hello guys! I've just found out about prefect not long ago and currently it a top candidate for our data workflow and pipeline. While i was going through the documentation, it stated that prefect 2.0 is under active development and prefect 1.0 is recommended for production use. Since prefect was officailly released a couple of days ago and is now the default installing package for pip, is it still true that prefect 2.0 is not recommended for production use? Is there also a way to visualize my workflow like in prefect 1.0's

flow.visuallize()

And also im really loving prefect and cannot wait to start working with it and exploring Thanks alot

Is it possible that some errors are not caught by Prefect when running multi-threaded code? PS: wasn’t sure if this is the right place to post since #prefect-server was archived.

hello, I’m struggling with loading a custom block from Prefect 2.0 cloud. I’ve created on cloud a block called

test

of a custom block type

Config

, and when trying to load its values within a flow with

Config.load('test')

I get this error:

except prefect.exceptions.ObjectNotFound as e:
>               raise ValueError(
                    f"Unable to find block document named {block_document_name} for block type {block_type_slug}"
                ) from e
E               ValueError: Unable to find block document named test for block type config

Hi, I’m struggling to find this in the docs for Prefect 2.0, does anyone know what the story is with breadth- vs depth-first execution? Is it automatically DFE for Dask and BFE for everything else, like 1.0?

Hello, I'm having a very frustrating problem with running prefect on our Google Cloud Platform Kubernetes Cluster and and hoping you can help me out. In short, a flow that was running fine on Thursday of last week suddenly gave vague errors on Friday when I tried to push an update. Is there a way I can get more details on the error from Kubernetes so I can debug this more efficiently? (logs and more examples will be posted in the replies shortly).

Hi - is there still a cloud based key/value store in prefect 2.0? I am having trouble finding it in the docs. Thanks.

Good morning, 2.0.1 question here: I am trying connect a Kubernetes OrionAgent to Prefect Cloud, and having some trouble.

Posting here for visibility: Prefect 2.0 interactive livestreams 3 times this week! https://prefect-community.slack.com/archives/C036FRC4KMW/p1659364260962609

Prefect 2.0.1 | Scheduling Hi! 👋 I’m trying to figure out how to set up a schedule (not using the UI). Is there a way to do it within the

prefect deployment build…

command? i.e. i have something like this in a bash script:

prefect deployment build flows/dbt_flow.py:dbt_primary_flow \
--name prod_flow \
--tag dbt \
--tag prod \
--tag daily \
-sb gcs/gcs-block \
-ib kubernetes-job/k8s-block

And I’d like to add something like

--schedule "cron/0 7 * * */Europe/Berlin"

If that’s not possible I guess I have to manually edit the deployment.yaml - if that’s the case, can I just put a cron expression in there, or do I need something else? I can’t find any examples in the docs, but maybe I’m just blind? 🙃

The links to the interface and the kubernetes flow runner appear to be broken in https://docs.prefect.io/tutorials/kubernetes-flow-runner/

Hi I’m trying to convert some v1 flows to v2 - just some simple snowflake queries at the moment but I sometimes get this error:

RuntimeError: Set changed size during iteration
Worker information:
    Approximate queue length: 0
    Pending log batch length: 0
    Pending log batch size: 0

I’m not trying to do anything with async but that appears to be where this is coming from (I guess it’s used via the

snowflake-prefect

integration?

Having a question for rename create_flow_run task, I think I post to the wrong channel https://prefect-community.slack.com/archives/C0192RWGJQH/p1659360778884719

In prefect 2.0, whats the alternative command of

$ prefect backend server

Hi everyone, I installed Prefect in a (mini)conda virtual environment on Windows Server 2019. Attempting to run a local flow gives this error, any thoughts? sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) table _alembic_tmp_deployment already exists [SQL: CREATE TABLE _alembic_tmp_deployment ( id CHAR(36) DEFAULT (( lower(hex(randomblob(4)))

Hi again, is there no longer a way to access flow-related context values inside a task? I’ve looked at this thread and it doesn’t look like it. In 1.0 I saved the flow run name as part of the metadata of my flow’s output products for traceability. I guess I can recapture this by grabbing the values in the flow and passing them into the task as a parameter, but wanted to know if I was missing something obvious

Hi, I have a pipeline where tasks need to be executed in their own containers. What is the best way of doing this? Is it to make each ‘task’ that needs to be executed its own Flow so that I can specify the image to be used, thus creating a Flow of Flows?

I am trying to add a s3 bucket block in cloud 2.0, however after clicking the add + button, I get a blank screen.

Hi! I am using Prefect 1.0, and am using different projects to support different deployment environments. Are there any suggested ways to isolate settings (e.g. secrets, env vars, schedules, …) between different projects?

Our Local Agents are up and running with the correct labels, yet they are not picking up jobs. The agent screen shows they are querying, and indicates many late runs for the agent. I have tried to restart the agent, but to no avail. There is no other hint as to what the issue might be. When I try a quick run of a flow, that does get executed. Any idea what is going on here?

Is prefect 1:00 not functional anymore? Also, how do we use prefect 2.0 on cloud?

Hi there! I wonder if there's a way of setting specific flows not to submit late runs. Thing is some of our flows, if submitted from "Late runs" might give us trouble