Orion requires sqlite 3.24.0 or later, and the aws docker image for lambda comes with sqlite 3.7. Does anybody know how to get the lambda docker environment to get the proper sqlite version to run prefect API calls through Orion?

Hi Prefect Experts - Im running 1.X of Prefect and run into the dreaded

"No heartbeat detected from the remote task"

issue a few times and its well documented here to consult https://discourse.prefect.io/t/flow-is-failing-with-an-error-message-no-heartbeat-detected-from-the-remote-task/79.

Hi Prefect team, when using DaskTaskRunner in a flow, is there a recommended pattern for using Dask features such as DataFrame and DaskBag? I’d like to be able to run tasks in the flow-instantiated cluster, then also take advantage of multi-node computation. I see that the

DaskTaskRunner

class has a Dask client under

self._client

, but it does not look like that’s intended to be used by the flow or tasks. Any tips are appricated!

Another question: How do I get task inputs in the Orion UI to populate?

Is there anywhere I can setup a notification if Prefect Cloud goes down. (touchwood never 🙂)

Hello, I have seen an interesting (to me) error: my code attempts to get the value of a secret, basically like this:

secret = prefect.client.secrets.Secret(SFTP_PASSWORD_SECRET_NAME)
    return secret.get()

...and it fails with a

prefect.exceptions.ClientError

from the GraphQL API.

Unrelated issue: this morning, tried to restart a 4-day-old flow run which had some failed tasks, it changed some of the task runs from "Failed" to "Pending", but they've been pending all day and aren't running. Is there something else I need to do? Other team members have recalled this always being the case in the past when they've tried to use the Restart feature as well. 🤔

Hi Prefect, Is there a way to configure a docker registry with credentials in a

KubernetesJob

? I want to pull a image from a private registry.

reception_deployment : Deployment = Deployment.build_from_flow(
    name="private-flow",
    flow=main_flow,
    output="deployment-private-flow.yaml",
    description="private-flow",
    version="snapshot",
    work_queue_name="kubernetes",
    infrastructure=KubernetesJob(), 
    infra_overrides=dict(
        image="myprivate-image:latest",
        env={},
        finished_job_ttl=300)
    )

I can not pull

"myprivate-image:latest"

Do I have to use

service_account

? 🤨 Thank you

How do I access the attributes of the class Flow inside the actual code for the flow I have created? For example,

@flow
def random_flow():
   id = Flow.flow_id
   return 1

How do I access any member say flow_id inside the flow, when it is being run?

Hi folks, what would be the correct way to use Blocks to load AWS S3 credentials in Prefect? Thanks! I posted the question at https://stackoverflow.com/questions/73864125/how-to-use-blocks-correctly-in-prefect --- UPDATE: Oh, I found the issue, the snippet misses an

await

. Posted the answer. Hi Prefect team, worth updating that demo. Thanks!

Hi, I don't understand how should I keep result of flows when the goal of the flows is to retreive datas

Am I on the right way with https://github.com/PrefectHQ/prefect/issues/6971 ? or is it an XY ?

Hi, i was looking for some help with triggering flow runs. how to trigger flow deployments with parameters?

Prefect 2.x should expand the documentation regarding production deployments. Such as for kubernetes jobs. Currently it's a lot of tinkering and digging trying to uncover and get everything to work. Way more then with the first prefect.

Hi, is there any official way how to install 2.x server on Kubernetes? It seems to me that the helm from prefect-server deploys 1.x with latest docker images.

Hi, is there any ways to order the parameters of a flow? For example, I want

start_datetime

and

end_datetime

to go together and start should comes first, not after like this

Hello, How can we use the

override

parameter in

prefect deployment build

to change kubernetes job parameters ?

Just as an FYI: If you edit a block and save it, empty fields are saved as empty strings. This works out fine most of the time, but the AWS credentials block does not work because (from the boto3 session.py):

if profile_name is None:
            return profile_map.get('default', {})
        elif profile_name not in profile_map:
            ....

So if you do not want to use a profile you have to overwrite

profile_name

manually with

None

in your code and then save it again. A fix would be, as an example, a checkbox next to nullable fields to set this field to null.

Has anyone tried out dbt-prefect in v2.. more specifically what sort of patterns would you use now?

Hi Team - When will the next release be for the Prefect UI project? I need to let my team know a timeline for this blocker. https://github.com/PrefectHQ/prefect/pull/6818

Hi guys, I am brand new to Prefect and trying to get familiar. I want my flow to finish in failed state but with a custom error message in the log and not the full exception detail:

from prefect import flow, task, get_run_logger

from prefect.orion.schemas.states import Failed

def my_function():

raise Exception('This is an exception')

@flow

def run_flow():

logger = get_run_logger()

try:

result = my_function()

<http://logger.info|logger.info>(result)

except Exception as e:

errmsg = f"Error! Type: {e.__class__.__name__} Detail: {e}"

logger.error(errmsg)

return Failed()

if __name__ == "__main__":

run_flow()

However, I get the following error; Exception has occurred: TypeError Unexpected result for failure state: None —— NoneType cannot be resolved into an exception File "main.py", line 21, in <module> run_flow() I'm thinking I might be doing more than one thing wrong here. Can anyone enlighten me, please? Thanks!

Hi everyone. I'm hoping someone can enlighten me on this - I'm thinking I'm missing something obvious but not seeing it. I'm utilizing the cli commands from

prefect-dbt

and can successfully execute a flow using the

trigger_dbt_cli_command

task, but dbt doesn't actually do anything.

For the new ECSTask - how does the image know which command to execute. For me it reaches the state "Pending" but in the container it just executes the default image entrypoint. The task definition command is empty (

[]

) in my yaml file the command points to my prefect entry script but it needs the UUID of the flow run. So it boils down to two questions: 1. How does the queue worker provide the UUID into the ecs task 2. What does

Command

do? (in the second screenshot I changed the task definition command from [] to

python3 /app/tasks/run.py

- but it still needs the flow run uuid)

Running into an issue referencing Anna's dataflow-ops template on deploying the ECS agent.

"containerDefinitions": [
      "entryPoint": [
        "bash",
        "-c"
      ],
      "command": [
        "prefect agent start -q ecs-worker"
      ],

results in error:

Usage: prefect agent [OPTIONS] COMMAND [ARGS]...

Try 'prefect agent -h' for help.

Error: No such command 'start'.

"containerDefinitions": [
      "entryPoint": [
        "bash",
        "-c"
      ],
      "command": [
        "prefect","agent","start","-q","ecs-worker"
      ],

results in what appears to be calling "prefect" with nothing else, as the logs just keep repeating the menu stdout:

Hello everyone. Does anyone know how the any_successful trigger would be implemented in Prefect 2.0?

is it possible in prefect 2 to determine the user who started a given flow run? in the prefect 1 UI it was visible but I don't see it anymore, not even in the run context

with the v2 logging, would it be possible to get logs that can handle color? e.g. dbt defaults in prefect look like:

Configuration:
  profiles.yml file [[32mOK found and valid[0m]
  dbt_project.yml file [[32mOK found and valid[0m]

Required dependencies:
 - git [[32mOK found[0m]

hi there, are there any examples of using FilterTasks in prefect 2.0? haven't found anything in the docs regarding these, so wondering if the path changed or if they were removed entirely

Just FYI we’ve been encountering errors when trying to pull secrets from the Prefect Cloud v1 vault.

[{'path': ['secret_value'], 'message': 'An unknown error occurred.', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}]

The interesting part is that this only seems to have to jobs at 9AM JST and 9PM JST. Which would be midday and midnight UTC.

Is it possible to separate tasks in different scripts from the flows that call them in Prefect 2.0? I'm getting this error currently. @task(name='Get Email Credentials', NameError: name 'task' is not defined

@task(name='Get Email Credentials',
      retries = 2,
      retry_delay_seconds = 10)
async def GetEmailCredentials(aws_credentials: AwsCredentials) -> EmailCredentials:
    session = aws_credentials.get_boto3_session()
    secrets_client = session.client(service_name='secretsmanager')
    aws_secret = secrets_client.get_secret_value(SecretId='DEV_EMAIL')
    secret_json = aws_secret['SecretString']
    emailDict = json.loads(secret_json)
    return EmailCredentials(emailDict)