https://flyte.org logo
Join Slack
Powered by
Hi all! Does Flyte has any retention policy for th...
# ask-the-community
g
Hi all! Does Flyte has any retention policy for the task output and input? The data is storing at 
user-raw-output/$DOMAIN/$PROJECT
and I found the output and input will disappear after 45 days.
d
I don't think Flyte applies retention policies at that level. Typically it comes from the blob storage configuration itself
g
Will the flyte version impact this? I found we rollout flyte from v.1.3.2 to v.1.11.0 at April 15, and all the workflows are failed to show input/output before April 15
The preview is different: pic 1: after April 15 pic 2: before April 15
@David Espejo (he/him)
d
ok but the executions work?
g
What do you refer to "executions"?
This tab works
Task also works
d
ok great, so if the execution succeeded as it seems to be, it means that the backend is able to find the inputs and write the outputs. The concern here is more about the preview in the UI?
g
Yeah
Users need to access those to debug issues or model calibration
It's empty
d
this is weird, I just ran the example workflow and I see the output:
g
Yeah the new workflow can show the outputs. The problematic workflows are those run on v.1.3.2, but it cannot be shown on v.1.11.0
d
oh now I see. Could you file an Issue for this? [flyte-bug]
s
g
Could you priority this ASAP? If there is quick workaround for this and it will be great
d
@Gilbert Yang seems like you found the root cause. Anything you could share about it?
g
It is a bucket policy that I have missed yesterday. The data has been deleted.
Open in Slack
PreviousNext
Powered by