Anders Segerberg04/12/2022, 4:20 PM
, with the
set to this file path.
Running the flow the first time, will write this key. Running it a second time, won't -- as expected, because of the idempotency behavior.
What I don't understand is that the second flow run has every task state set to 'success' -- but wouldn't I expect them to be 'cached' or something else, indicating that the flow isn't being re-ran?
task is just an API call with the same key that will return the already ran flow
Anders Segerberg04/12/2022, 4:31 PM
Anders Segerberg04/12/2022, 4:34 PM
that flow, I would expect the state to be
I'm not sure how to get to the subflow page.Technically, there are no subflows in Prefect 1.0. You just navigate to your flow page of the respective (child) flow
Clicking on the "task" that amounts to the started flow run, and running 'restart' there, doesn't seem to indicate any cache behavior.Restarts are intended to be used when something fails, not to rerun any arbitrary task when needed.
So if ICaching is a separate feature and it applies to tasks, not to (sub)flows and it's used to avoid expensive recomputation. If you need more examples for the flow-of-flows, I recommend looking at some examples here and also create_flow_run examples.that flow, I would expect the state to be
Anders Segerberg04/12/2022, 5:35 PM