Hey, congrats on releasing 2.6.5. Why is it, that for manual retries via UI we need to enable result persistence? Don't we simply rerun a flow - why do we need the results from the failed flow to be persisted? (Not that it's a problem, I'd just like to understand the underlying architecture)

When you run it again, we will automatically restore all of the completed task run states. If you use these downstream, they’ll fail when their result is retrieved (if persistence is disabled).

That sounds great!

Ah I see. If I understand correctly, you don't rerun already succeeded tasks. This is very nice!! Thanks for clarifying 👍