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. I’d really appreciate any ideas or suggestions! Thank you! # Answer Currently, Flyte does not support setting a TTL for cache entries on a per-task basis. The TTL is configured globally in the FlytePropeller configuration, which means it applies to all tasks uniformly. This has been a topic of interest, and there are discussions about adding this feature to allow more granular control over cache expiration (source, source). Would you like more details on how to configure the global TTL or any other related information? Sources: - https://discuss.flyte.org/t/15638766/hello-wave-is-there-a-ttl-on-how-long-the-tasks-will-be-cach/ - https://github.com/flyteorg/flyte/issues/3305 Slack Link https://flyte.slack.com/archives/CP2HDHKE1/p1732811047.201809 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.