cuddly-jelly-27016
08/24/2025, 12:10 AMdynamic_workflow in remote it will not cache the intermediate df even if the type-hint can be extrapolated and Flyte knows that the type is cacheable. Interestingly this deviates from local execution as locally the cache is hit correctly.
### Expected behavior
Cache should be hit for successive executions assuming no changes in output of load_wine.
Reasons for the bug:
The difference is between how promises (also called bindings at runtime) and Literals are modeled.
Literals have a hash value field - here, on the other hand Bindings do not - here.
flytekit when creating a binding at runtime for a dynamic workflow, simply populates the scalar value and ignores the hash field - here, here, here and here
Solution:
Add a hash field to bindings and ensure that is populated in dynamic workflows.
We should also make flytekit always use a common method to transform either a promise to binding data or a literal to binding data
### Additional context to reproduce
No response
### Screenshots
No response
### Are you sure this issue hasn't been raised already?
• Yes
### Have you read the Code of Conduct?
• Yes
flyteorg/flytecuddly-jelly-27016
08/24/2025, 12:10 AM