I couldn't find a hello@prefect.com email to direct this at so apologies for dropping it here. I've been looped in to help with some last minute promotion/sponsorship for PyData Miami which is taking place next Thursday (9/22/2022): https://pydata.org/miami2022/ There is sponsorship opportunities if you think Prefect would be interested: https://pydata.org/miami2022/wp-content/uploads/2022/08/PyData-Miami-2022-Sponsorship-Prospectus-1.pdf You could also encourage attendance to your colleagues and network. Let me know if you have any questions.

After installed Prefect Orion 2.4, getting the following error while starting Prefect Orion. Please help me to fix this issue. sqlalchemy.exc.ProgrammingError: (sqlalchemy.dialects.postgresql.asyncpg.ProgrammingError) <class 'asyncpg.exceptions.UndefinedObjectError'>: operator class "gin_trgm_ops" does not exist for access method "gin" [SQL: CREATE INDEX CONCURRENTLY trgm_ix_flow_name ON flow USING gin (name gin_trgm_ops); ]

Do you know if it would be possible to convert the snowflake_utils to work with the SnowflakeConnector block? I’ve had a try but I get invalid username/password although I’ve used the same block in snowflake_query without an issue

Hello. I’m starting to see a low of flows runs crashing when trying to update task state (500 error from https://api.prefect.cloud/api/accounts/<uuid>/workspaces/<uuid>/task_runs/<uuid>/set_state) Full stack trace in the thead. Is there any way to diagnose further?

We are getting a flow failure with this message:

Submitted for execution: Task arn:aws:ecs:us-west-2:<>:task/prod-prefect-cluster/c01a3ca13b3741a89e58b6c33dda0671
INFO prefect-server.Lazarus.FlowRun Rescheduled by a Lazarus process. This is attempt 1.

Any tips on how to debug this? I can’t find the logs for these tasks in cloudwatch.

Question regarding trigger.any_failed:

Hi Team - When running my docker image in the terminal. I wanted to get a list of block types: prefect block type ls There was an aws credential block type, but I am not able to create it, nor see that type in blocks. Is this a type that was abandoned?

Is it expected that this graphql query would return a flow group id rather than an actual flow id? Does

client.create_flow_run

work off of flow group ids?

{
  flow(
    where: {name: {_eq: "FLOW_NAME"}, archived: {_eq:false}},
    order_by: {created: desc}
  ) {
    id
    name
    project {
      name
    }
  }
}

The concept of Agent and Work Queues is really useful. But as far as I understand, Work Queue's hold only flows, not tasks. What queue do tasks go into? Is there a way for a user to tap into that queue?

Hi I have

main

flow, which calls to a subflow

go_eat

, each time with different parameters. something of the sort:

@flow
def go_eat():
    ...

@flow
def main():
    animals = ['dog', 'cat', 'monkey']
    for animal in animals:
        go_eat(animal)

I want to make those

go_eat

flows to run in parallel, and I wonder how to implement this. it would be best if I could make up to 2 animals to

go_eat

in parallel, but no more than that. I'm not sure if I somehow better use the prefect queue concurrency mechanism, or if I better implement this in pure python. any suggestions?

Hi, We are getting an error when trying to login to Prefect Cloud 2.0:

Hello Everyone. Quick questions. My prefect flow failed and the logs are not helping that much. I get a long stack trace error without anything specific. How can I know that I have a problem with the infra, or with the code ? If you need more details please help me frame my question better.

Heya! I’m new to prefect and am trying to deploy a local agent

prefect deployment build flows/redshift_mv_refresh.py:redshift_mv_refresh --name JPMBP-O --queue JPMBP-O --tag "redshift mv-refresh test" --infra process

However I’m running into an issue where the

deployment build

command tests the main flow and hence fails as it can not import some of the modules provided by a virtual env.

...
    import redshift_connector
ModuleNotFoundError: No module named 'redshift_connector'
...
prefect.exceptions.ScriptError: Script at 'flows/redshift_mv_refresh.py' encountered an exception
An exception occurred.

my project’s directory

❯ tree . -L 2
.
├── flows
│   ├── __pycache__
│   ├── lib
│   └── redshift_mv_refresh.py
├── requirements.txt
└── venv
    ├── bin
    ├── include
    ├── lib
    └── pyvenv.cfg

How can I tell

deployment build

to look for python in

venv/bin/python

Thank you a bunch! edit: I’m using Prefect 2 with Cloud.

Hi. What is the replacement for projects in Prefect 2? How to group flows? Thanks.

Hello everyone, I'm looking to migrate from 1.0 to 2.0 and it seems that some functionality is missing. Back in 1.0 we were running a k8s agent and the flows where stored in a private Github repo. In Prefect 2.0, I wasn't able to find a way to connect to a private Github repo. I tried also to store the flows in GCS, however the agent didn't had the required library to connect and download the flows from it. Any chance I'm missing something?

Is it possible to provide a list object as a parameter in Prefect Cloud 2 offering? When I input

['analytics.mv_1', 'analytics.mv_2']

in the Parameters form, the parameter is treated as a string 😞

...
13:31:26.728 | INFO    | Flow run 'lush-bettong' - Scheduling materialized views {mat_view_names}
13:31:26.729 | INFO    | Flow run 'lush-bettong' - Refreshing materialized view '['
13:31:26.735 | INFO    | Flow run 'lush-bettong' - Refreshing materialized view '''
13:31:26.737 | INFO    | Flow run 'lush-bettong' - Refreshing materialized view 'a'
13:31:26.739 | INFO    | Flow run 'lush-bettong' - Refreshing materialized view 'n'
13:31:26.741 | INFO    | Flow run 'lush-bettong' - Refreshing materialized view 'a'
13:31:26.745 | INFO    | Flow run 'lush-bettong' - Refreshing materialized view 'l'
...

Hi is there any Guide for the AWS setup necessary for a Prefect

ECSAgent

? I don't quite manage to get it right. Thank you! The Agent registration is successful, I start the Flow, in AWS the task is created but the TaskDefinition is INACTIVE and the Task itself is PENDING

Hi, I was trying to find out in the Prefect 2.0 docs the equivalent of Prefect 1.0's context, as I would like to get the scheduled start time of the flow run inside the flow itself (or one of its tasks). Is it possible to do it? Thanks!

Hi, i was trying to trigger two independent flows (say flow1,flow2)from a parent flow while passing params(dict) from parent to flow2...flow2 is sorting the dict param received from parent..Can someone clear this out?Thanks. the later image shows the received param

Hello. I have a

WebHookAction

Automation set up that keeps generating false failure notifications on Cloud UI. The WebHook sends an HTTP POST to a specific endpoint and returns an HTTP 202 status code upon success, but Prefect seems to think it's an error. Every time the action triggers, I get a new failure notification. This literally spams our Cloud Notifications with false failures. FYI this issue seems to be the exact same issue, but I was told it wasn't, and to open a new ticket (I still think it's the same issue): https://github.com/PrefectHQ/prefect/issues/5955 Screenshot of false failure notification:

Hi again! Getting busy using Prefect 2 🙂 I’ve never worked with Prefect 1, but looking at the screenshots, there is an Agent tab available.. Do we have something like this in Prefect 2 UI? Might be subjective opinion, but anyway.. looking at Prefect 1 UI screenshots, it looks much more fleshed out than Prefect 2 UI. To your knowledge is the Prefect 2 UI work in progress and hence should I focus on using Prefect 1 for production use?

Hello! I was wondering: in Prefect 2, is it possible to leverage on multiple deployments to pass different parameters to the same flow?

hello prefect team, hello community, i am currently setting up a deployment for a flow with a couple of boolean parameters with default values in prefect 2 and noticed that these are nicely displayed as switches in the flow run creation form. The switches are set to "False" irrespective of the actual default value. When these switches are not changed during the flow run creation, the flow run will be submitted without these parameters, and consequently using the default settings that could be "True". This results in a mismatch between what the user sees on flow submission and what's actually executed. However, if the switches are toggled back and forth, effectively resulting in the same state of the form, the flows are submitted with the parameters from the form, overwriting the default parameters. This means that toggling the switches back and forth results in a different outcome than not touching the switches at all, even though the form looks exactly the same. i think this could lead to some very hard to reproduce issues. where should i submit UI related bug reports? Please find an example flow in thread. Thanks a lot

With prefect 2, I'm seeing issues when attempting to get flow groups via the api (using the cloud product). If I try to filter by flow group state, I get a 500 response, but if i omit that the request is fine.

Hey all, when the UI queries the API and fails, there is no indication in the UI, even a small badge would be helpful. I think this has been raised on GitHub but I am not sure. Does someone know if this is on the future plans?

Hello, I cannot seem to run more than one k8 job at a time. If I try to kick off two jobs the first runs but the second job fails with a 500 error.

I'm currently trying to implement Docker with prefect, but following Anna gellers repo with dockerfile, the docker build fails on both the copy and add line (2 and 4) anyone had the same issues or ideas of how to resolve it?

Hello all. I've been trying to deploy prefect 2.0 agent to an ec2 instance and been having issues. I tried following this page however it did not work. https://discourse.prefect.io/t/how-to-deploy-a-prefect-2-0-agent-to-an-ec2-instance-as-your-execution-layer/551 I was able to get the agent to run in the ec2 instance but when I would run a deployment it was just stay stuck on pending. The agent would pick up the flow and submit flow run but wouldn't run. Any help on how to get the agent running will be appreciated. Thank you, Taylor

I was just curious why all these jobs stay around with the helm prefect-agent. I am using the most recent version of prefect-agentalso. Cuz I can't view the logs for previous jobs, it says

Stream closed EOF for prod-prefect/analytic-shrimp5rkr9-j82lj (prefect-job)

for all of them. Are they supposed to auto delete?