Hi. I am refactoring. I divided my flows into 3 categories: • pipelines: Takes input from upstream pipe and feeds downstream pipe. Pipes are tube together with flow.update(pipe_file_reader) , flow.update(pipe_transform) and so on. • python parametered flows: Takes input such as pandas dataframe through 'Parameter' task. These are for paralelism with create_flow_run.map(flow_name) • production flows: End product flows These will be the sub folders of pipelines in my project. Any idea is appreciated!

@Toprak Nihat Deniz Öztürk thanks for sharing your flow structure. Is there anything you need help with or did you just want to share? if you have some issues in packaging this, perhaps this repo can help: https://github.com/anna-geller/packaging-prefect-flows/

I don’t think you can pass a Pandas DataFrame through a Parameter. Parameters need to be JSONSerializable because they are passed through the API so you can’t really pass complex Python objects.

@Kevin Kho I test my flows with flow run and forgot about graphql. I am not sure about pipes approach too. I probably get <name "..." is not defined> error if I put flows in seperated files. Need a way to work around.

For the pandas dataframe specifically, your parameter can be a location to where it lives and then you can load it in