Hey Flyters, I think we are experiencing a bug with overwrite cached outputs flag in the UI. I used overwrite cached outputs for a workflow, which then showed that task x successfully wrote the output to cache (cache version 0.0.1). I relaunched the workflow with different parameters(without overwrite flag) which shouldn't affect task x. the task read from cache version 0.0.1, but it wasn't the overwritten output, it was an older cached output for this version. (I compared the s3 links). Is this a known bug?

seems like a bug to me. the cache needs to be hit, but the overwritten cached outputs should be used, correct?

Yes exactly

would you mind creating an issue? [flyte-bug]

🐞 Create a new Flyte Bug issue: https://github.com/flyteorg/flyte/issues/new?assignees=&labels=bug%2Cuntriaged&template=bug_report.yaml&title=%5BBUG%5D+

Sure. thanks