@Marvin Is it possible to dynamically name a task? I have a defined task/function that gets executed multiple times in a flow. I Want the task in the UI to have a descriptor that includes information on the input arguments, is this possible?

@Marvin I am using this yaml to do prefect

deploy --name my_pipeline

. How can I do the same with a python script and not via the CLI?

# File for configuring project / deployment build, push and pull steps

# Generic metadata about this project
name: my-pipeline
prefect-version: 2.12.1

# build section allows you to manage and build docker images
build:
  - prefect_docker.projects.steps.build_docker_image:
      image_name: <http://mycompany.azurecr.io/dir/prefect-image|mycompany.azurecr.io/dir/prefect-image>
      tag: latest
      dockerfile: Dockerfile
      push: true
      credentials: "{{ prefect.blocks.docker-registry-credentials.my-cred }}"


# push section allows you to manage if and how this project is uploaded to remote locations
push: null

# pull section allows you to provide instructions for cloning this project in remote locations
pull:
  - prefect.projects.steps.git_clone_project:
      repository: <https://bitbucket.org/mycompany/repo.git>
      branch: master
      access_token: "{{ prefect.blocks.secret.bb-credentials }}"
  - prefect.projects.steps.set_working_directory:
      directory: /opt/prefect/repo

deployments:
  - name: my_pipeline
    description: TODO
    entrypoint: my_pipeline/my_pipeline.py:my_flow
    parameters: {}
    work_pool:
      job_variables:
        image: "{{ image_name }}"
      name: worker_pool
      work_queue_name: default

@Marvin is it possible to set nodeSelector and tolerants on a work pool so that all flows described in my prefect.yaml that are associated with that work pool will be scheduled on a specified node pool?

Is there a callback for when a flow starts? I see there are callbacks for on_completion and on_failure

Hey, does anyone in the community did incremental etl with Prefect ? We are considering doing it and maybe there are mistakes that can be avoided ^^ Thanks !

Is this heartbeat configuration only applicable to Prefect cloud setups? https://docs.prefect.io/orchestration/concepts/services.html#heartbeat-configuration I have a (expected) long running job on a Prefect server setup trying to not have the zombie killer terminate the job:

No heartbeat detected from the remote task; marking the run as failed.

Have you seen this issue when launching jobs from the ECS Agent? I'm troubleshooting and not sure where to start with it. botocore doesn't like something about the parameters. Prefect version is 1.0

Hi, a newbie question… If the trigger for all tasks in a flow is “all successful”, and one of the upstream task fails, all of the downstream tasks are “trigger failed” (even if the upstream failed task is restarted and succeeds). This forces me to restart the trigger-failed tasks one by one. Is this the intended behavior? or am I missing something? Should I change the trigger to “all finished” in order to avoid this manual restarting of the downstream tasks when one of the upstream tasks fails at least once?

Ok so I updated to the latest and I'm still getting this bug:

File "/home/dave/.cache/pypoetry/virtualenvs/rustmonster-GKhQY2Y4-py3.10/lib/python3.10/site-packages/prefect/client/orchestration.py", line 219, in get_client
    server.start()
  File "/home/dave/.cache/pypoetry/virtualenvs/rustmonster-GKhQY2Y4-py3.10/lib/python3.10/site-packages/prefect/server/api/server.py", line 818, in start
    raise RuntimeError(error_message)
RuntimeError: Timed out while attempting to connect to ephemeral Prefect API server.

@Marvin I don’t see my deployments or the flows on the dashboard, but I can see them when I go to the cli and run

prefect deployment ls

what could be the problem?