New RunLLM response generated: >>>*# Question* Hey community! TLDR: can you delete FlyteExecutions/results via the flytekit/flyte-backend, and if not, can you at least invalidate their cached status? We store our task results on S3. For data management, it is sometimes useful to delete these s3-based results from flyte executions (for failed jobs, for example, even though some tasks may have succeeded) - or just really old jobs, because we don't like our large s3 bill. The problem is that if you delete the s3 result data for a task that wrote to the cache, a later task will still behave as if it receives the cached result, but it will be "0", and the task will fail. It would be best if you could interact with flytekit and tell it to just delete an execution and all results (also invalidating any cache status). I think I wrote about this before, and was told this was intentionally not implemented because it seemed too complex, too dangerous, too many edge cases. But you can't expect people to keep data on s3 forever. Should we just interact with the flyte backend database to delete entries directly? This feels a bit dangerous and brittle, prone to break when your schema changes, and I'd prefer an API to deal with this. What is the best practice here? # Answer Currently, Flyte does not support direct deletion of executions or their results via Flytekit or the Flyte backend. The primary reason is to maintain data lineage and reproducibility, which are core principles of Flyte. However, you can archive executions, which is a safer alternative to deletion (source). For cache invalidation, Flyte does support evicting cached task outputs. You can use

flytectl

to update an execution and evict its cache, which can help manage storage costs and avoid issues with stale cache data (source). Would you like more details on how to use

flytectl

for cache eviction? Sources: - FlyteCTL Feature: Delete projects - RFC for Eviction of cached task outputs Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1725464907.129129 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.