New RunLLM response generated: >>>*# Question* Hi everyone, I’m exploring Flyte's caching mechanism and was wondering if there’s a way to configure a time-to-live (TTL) for the cache. Specifically, I’d like to set the cache to persist for a defined duration. Any insights? Thank you! # Answer Currently, Flyte's caching mechanism does not support setting a TTL on a per-task basis. The TTL is managed globally through the FlytePropeller configuration using the

max-cache-age

parameter, which defines how far back in the past the cache can be queried. This is a global setting and not configurable at the task level (source, source). Would you like more detail on how to configure the global TTL or explore potential workarounds? Sources: - Flyte Community Discussion on TTL - Flyte Community Discussion on Caching Slack Link https://flyte.slack.com/archives/CP2HDHKE1/p1732797663.363709 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.