Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

indeed! <https://docs.flyte.org/projects/flytekit/en/latest/generated/flytekit.dynamic.html#flytekit-dynamic>

Interesting.. I was confused because in the console I don't see the little check mark next to it to indicate that the output was written to cache

ooo, would you mind taking a screenshot and posting here?

n1 and n2 are dynamic with caching enabled

Do I need to also enable caching in the called tasks for the cache at the dynamic task to work?

hmm, so the dynamic workflow cache should be independent of the caching of tasks invoked within it.

<@U0231BEP02E> dynamic workflows should have a circle-y checkmark thing if it’s cached, no?

sry missed this message. checking the cache dynamic workflows...

<@U03HQE6THNV> really sorry for the late reply. yes. the dynamic task can be cached, and it should show on the UI. However, there is a bug in the Flyte console which first time when execute the dynamic task it won’t show any cache icon (it should show `cache_populated`), but the second time when execute the dynamic task with the same input, it should said `cache_hit`  Please let me know if you have further questions or face any issues :slightly_smiling_face: