Hi all. Is there a way to filter out default prefect logs like:

Starting task run...
[2022-10-25 15:23:07+0100] INFO - prefect.TaskRunner | Task 'read_features_config[1]': Starting task run...
[2022-10-25 15:23:07+0100] INFO - prefect.TaskRunner | Task 'read_features_config[3]': Finished task run for task with final state: 'Success'

hello, why my flow always stuck at Pending State with the agent log like:

I found the explaination here, but seems like it's for prefect 1, there is no --show-flow-logs in prefect 2

hi! im trying to use my postgres db running on rds as the database for orion(self hosted instance) backend. but it continuously runs into time out errors. has anyone implemented this before or facing the same issue ?

Hello all, does anyone know what the Prefect Cloud retention policy is for flow and task results, and how large the

location

field may be (i.e. for use with

PrefectResults

)? Thanks!

Hi team, I’m a bit lost in how to configure JSON logging in Prefect 2.0. I see this concept document and this api reference on the JSONFormatter, but I can’t seem to find how to marry the two together. What we’re trying to achieve is: 1. Prefect Cloud 2.0 still shows logs as is 2. Kubernetes jobs output logs in JSON so that they can be ingested by datadog (we want each log entry to have the flow_name, task_name, etc. to make it easily searchable back in time).

Hi folks, quick dumb question : to set to the type of parameter for a flow, do i just use type hints to set the type of parameters?

Hi All, I keep getting the below Timeout error while fetching data using graphql in a python code for Prefect 1.0 prefect.exceptions.ClientError: [{'path': ['flow_run'], 'message': 'Operation timed out', 'extensions': {'code': 'API_ERROR'}}] Is there any solution to avoid this?

Hello, I'm trying to deploy prefect agents on an on prem environment, but I get a

prefect.exceptions.PrefectHTTPStatusError: Client error '403 Forbidden' for url '<https://api.prefect.cloud/api/accounts/xxxxxxxx/workspaces/xxxxx/work_queues/name/dev-prem-wq>'

I tried changing the api keys (service account) / giving ownership to the agent on the workspace, but nothing worked so far. I tried deploying the agents on the cloud on a kubernetes cluster and it works just fine, but when I try to do the same thing on our on prem environment, it returns me this error. Can I have some insights please ? Thanks

@Nate Hi Nate, I suppose to have a meeting with you tomorrow at 8PST I did not get the email invite from https://calendly.com/ (yet) Youval

Fugue is a unified interface for distributed computing that lets users execute Python, pandas, and SQL code on Spark, Dask and Ray without rewrites. prefect-fugue provides the Fugue tasks, context and blocks for Prefect. In Prefect Live at 3PM Eastern today, Kevin Kho, a former community engineer at Prefect, will talk about how to use this integration and its use cases. Come join us live on Twitch. Subscribe to Prefect Community Calendar, available at prefec.tv/calendar, to get updated with all Prefect Live events.

Hey hi - prefect noob here - we’re using Prefect 2.0 w/ Prefect Cloud in a new system were building, and I have a couple Q’s around secrets. Details in the thread - thanks in advance!!

Anyone seen mapped (one of the mapped runs) hanging forever when running in prefect-server with LocalExecutor?

Hi, I've been moving my workflow orchestration into Prefect, and recently ran across some strange hanging behavior in moving from one task to another which I'm hoping someone can shed some light on. This behavior was observed running Prefect 1.4.0 from windows cmd. I saw it on two different flows so far, and it's a bit inconsistent. What I'm seeing is that one or more of the tasks will have completed (according eg to the logs generated by the actual task), but then it hangs right at the end. When I press Ctrl-C (the first time was to try to abort the run since that's the usual behavior), instead of aborting it seems to prod it into acknowledging that the task completed successfully and it then moves on the next task. I haven't been able to rerun much to test since these are large flows that takes more than a day to run, but in each case I've seen it happening in a few of the tasks but not others, and in one case I was able to rerun for test purposes, and it happened again, but on a different step from the first time. I'm going to post some more details in a thread.

Hey can someone help me diagnose an issue I have just come across using '1.4.0' - I am suddenly getting;

AttributeError: 'Context' object has no attribute 'scheduled_start_time'

Hello! I have an Azure block to store my flows, how can I store the flows in different folders within my block?

Back again with what look like Prefect 2.0 API load issues? My first question is how would I debug the following? I don't have an exception being caught and I think this is a crash inside prefect code, not mine.

13:00:10.647 | ERROR   | Task run 'Get-Items-d8ed86f1-212' - Crash detected! Execution was cancelled by the runtime environment.
13:00:10.650 | ERROR   | Task run 'Get-Items-d8ed86f1-15' - Crash detected! Execution was cancelled by the runtime environment.
13:00:10.652 | ERROR   | Task run 'Get-Items-d8ed86f1-857' - Crash detected! Execution was cancelled by the runtime environment.
13:00:10.653 | ERROR   | Task run 'Get-Items-d8ed86f1-774' - Crash detected! Execution was cancelled by the runtime environment.
13:00:10.654 | ERROR   | Task run 'Get-Items-d8ed86f1-609' - Crash detected! Execution was cancelled by the runtime environment.
13:00:10.655 | ERROR   | Task run 'Get-Items-d8ed86f1-444' - Crash detected! Execution was cancelled by the runtime environment.
13:00:10.657 | ERROR   | Task run 'Get-Items-d8ed86f1-399' - Crash detected! Execution was cancelled by the runtime environment.
13:00:10.659 | ERROR   | Task run 'Get-Items-d8ed86f1-700' - Crash detected! Execution was cancelled by the runtime environment.
13:00:10.660 | ERROR   | Task run 'Get-Items-d8ed86f1-460' - Crash detected! Execution was cancelled by the runtime environment.

hello! is there a way to deploy flows with non-JSON serializable arguments?

I’ve run into an issue with switching my backend database from the default sqlite instance to a postgres instance. Most of the blocks (in particular for my use case the Azure block) are no longer available in the UI and they don’t show up in the postgres db. Do I need to register them specifically now that I’m using a different db?

Hi Prefect Experts - Im running Prefect 1, but running into an issue that Im having a hard time tracking down. We have Prefect deployed on Kuberneters and are using Dask Executors. The general pattern is: users submits a flow agents creates a job pod job pod creates a dask cluster (minimum of 1 scheduler and 2 workers) tasks run on the dask workers The job pod is consuming memory until it crashes.

Hi team, is this the right place to get help on setting up my account for Prefect 2.0 Cloud? My account is in a weird state. Workspaces empty, organizations empty. Can’t create a new workspace either as the Owner dropdown has no entries. Noticing a lot of 403 entires in the devtools console.

Hello everyone, How could you pass different parameters in deployments through python? In my flow: @flow(name="Master of flows") def Master_flow( t: str='defecto' ): task_data(t) then in my deployment script: deployment = Deployment.build_from_flow( flow=Master_flow, name="docker_azure_flow", version=1, work_queue_name="default", parameters={'t':'parametro pasado'})

With prefect v2, is there a way to kill a flow run in UI? I notice that deleting the flow run won't terminate the process, instead my agent crashed and throwed a 404 error 🤔

Hi team, is there are any documentation around how Blocks data is stored securely in Prefect Cloud 2.0. If we were to use blocks to store database credentials it would be great to know how these are stored on your side.

Is there a way to set a flow concurrency limit on the agent itself? As far as I can work out, work queue limits aren't going to work when we have multiple agents per queue, and agents that listen to multiple queues at the same time (with

agent start --match

). All I need to tell each agent is "Don't start more than N docker containers at the same time" (or you will run out of disk or memory)... E.g. the limit is really on the agent resources. In the full cloud I don't care how many things run simultaneously - the more the merrier :D

Hi. Quick question: I have received an error for Prefect 1.x because my order of returned parameters was a little bit messed up, interchanged 3 parameters for a prefect task and one ended up missing. And the error I got was pretty weird, something in the lines of `ValueError: Could not infer an active Flow context while creating edge to <Task: Task1>. This often means you called a task outside a

with Flow(...)

block. If you're trying to run this task outside of a Flow context, you need to call `GetItem(...).run(...)`` . All in all error was because of missing params from function call. Could you make the error a little bit more helpful ? Or specific ? ...... Or am I missing something ?

How do we use the prefect string and secret blocks in an ipynb file? It works fine in py files, but when using then in notebooks i get following error

Hi team, could someone give me some guidance on how we can pass in an

envFrom

section to a

KubernetesJob

block. We want to include this using the Python API:

envFrom:
            - secretRef:
                name: job-secrets

is prefect 2.0 the same as orion? are they aliases to each other?