Channels
pacc-july-11-12-2023
pacc-sept-20-21-2023
pacc-aug-16-2023
pacc-aug-29-30-2023
pacc-may-31-2023
prefect-ai
pacc-clearcover-june-12-2023
pacc-sept-26-27-2023
pacc-july-6-2023
intros-test
livestream-chatter
marvin-in-the-wild
data-ecosystem
geo-israel
pacc-june-14-2023
geo-japan
pacc-london-2023
pacc-sept-13-14-2023
prefect-cloud
ppcc-may-16-2023
prefect-azure
prefect-docker
prefect-recipes
gratitude
geo-nyc
geo-bay-area
geo-boston
geo-london
geo-dc
geo-chicago
geo-berlin
geo-texas
geo-seattle
geo-colorado
pacc-july-17-18-2023
introductions
prefect-server
data-tricks-and-tips
prefect-aws
prefect-gcp
find-a-prefect-job
prefect-dbt
random
events
ask-marvin
show-us-what-you-got
prefect-getting-started
prefect-integrations
prefect-contributors
best-practices-coordination-plane
announcements
prefect-ui
prefect-kubernetes
pacc-aug-22-23-2023
prefect-community
Powered by
#prefect-community
Title
v
Vitaly Shulgin
09/28/2020, 8:39 AM
Hello team, previously I was asking to clarify why it is impossible to register new flow from parent flow, here
https://prefect-community.slack.com/archives/CL09KU1K7/p1600240447350500?thread_ts=1600209791.334200&cid=CL09KU1K7
Could you bring some light on that case? Like cold system start, where the one parent flow creates many new flows, initially stored in git or database. What will be the way to accomplish it with current prefect funcionality?
c
Chris White
09/28/2020, 3:11 PM
Hi Vitaly - you could try to call
flow.register
from within a task; we don’t have a recommendation for this pattern yet, so you should give it a shot and let us know how it goes!
Post