Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

:wave: Hello, team! I just signed on and hope to find answers for accessing task results.

Welcome to Prefect, <@U03DB58QK7Y>! Just catching up on Slack and Discourse - have you already posted your question about task run results somewhere?

Hi Anna,

No, I'm doing 2 things at once, but I first want to have a look at the resources.

I found out that if I just run an imperatively-defined prefect task by calling its run() method, I can avoid all the flow paraphernalia. That leaves me with a different problem, which is how to manage the input parameters (and results). They should be hidden in the flow and not mess up the Action instances.  Actions are my addition.

I had to google what is "paraphernalia" :joy: TMYK!

generally speaking, if you are just getting started with Prefect, it's easier if you start directly with Prefect 2.0. Orion is able to run arbitrary Python code, so you may just use the flow decorator for your workflow and altogether avoid all the DAG-"paraphernalia" :slightly_smiling_face: if you need some resources about that, check those:
• <https://discourse.prefect.io/t/should-i-start-with-prefect-2-0-orion-skipping-prefect-1-0/544>
• <https://orion-docs.prefect.io/getting-started/overview/>
&gt; how to manage the input parameters (and results)
for parameters, I wrote a detailed post <https://www.prefect.io/blog/how-to-make-your-data-pipelines-more-dynamic-using-parameters-in-prefect/|here> for 1.0 and for Results you may check  <https://docs.prefect.io/core/concepts/results.html>