In prefect 1 0 you could use the `upstream tasks` argument t Prefect Community #ask-community

Channels

data-tricks-and-tips

feedback-deployment-concurrency

find-a-prefect-job

livestream-chatter

marvin-in-the-wild

pacc-apr-10-11-2024

pacc-apr-30-may-1-2024

pacc-apr-9-10-2025

pacc-aug-16-2023

pacc-aug-22-23-2023

pacc-aug-28-29-2024

pacc-aug-29-30-2023

pacc-clearcover-june-12-2023

pacc-dec-17-18-2024

pacc-feb-13-14-2024

pacc-feb-26-27-2025

pacc-jan-28-29-2025

pacc-july-11-12-2023

pacc-july-17-18-2023

pacc-july-30-31-2024

pacc-july-6-2023

pacc-june-14-2023

pacc-june-20-21-2024

pacc-london-2023

pacc-london-sept-2024

pacc-mar-12-13-2024

pacc-may-31-2023

pacc-nov-19-20-2024

pacc-nov-8-2023

pacc-nyc-may-2024

pacc-oct-11-12-2023

pacc-oct-1-2-2024

pacc-oct-16-17-2024

pacc-sept-13-14-2023

pacc-sept-20-21-2023

pacc-sept-26-27-2023

ppcc-may-16-2023

prefect-contributors-archived

prefect-getting-started

prefect-integrations

prefect-kubernetes

prefect-recipes

In prefect 1.0 you could use the `upstream_tasks` ...

# ask-community

j

Jacob Goldberg

07/07/2023, 4:49 PM

In prefect 1.0 you could use the

upstream_tasks

argument to manually block one task on others, is there an equivalent in prefect 2.x?

✅ 1

Jacob Goldberg

07/07/2023, 4:50 PM

nvm. found the answer here

c

Christopher Boyd

07/07/2023, 6:18 PM

wait_for

?

👍 2

👆 1

2 Views