Here’s the response I got from Zapier Support about this topic:
Are you looking at this from a dev perspective, or as a customer (as it can be different, based on how a dev uses our hydration routines.) I'll try to cover both.
If you are a dev, and using stashing, these s3 links/files will live for 30 days - more on that process here: https://github.com/zapier/zapier-platform-cli#stashing-files. As a customer, these links would also live for 30 days...
If your app or the app you are using doesn't stash a file, then you won't see an S3 link, but a hydration object, and that time is less than a week, but also the file it points to might only be available for even a shorter time (it would be up to the app to determine).
Here’s the response I got from Zapier Support about this topic:
Are you looking at this from a dev perspective, or as a customer (as it can be different, based on how a dev uses our hydration routines.) I'll try to cover both.
If you are a dev, and using stashing, these s3 links/files will live for 30 days - more on that process here: https://github.com/zapier/zapier-platform-cli#stashing-files. As a customer, these links would also live for 30 days...
If your app or the app you are using doesn't stash a file, then you won't see an S3 link, but a hydration object, and that time is less than a week, but also the file it points to might only be available for even a shorter time (it would be up to the app to determine).
Thanks @Troy Tessalone , regarding the Hydration Object is there a guaranteed minimum retention period?
That’d be a question for Zapier Support, but when in doubt, don’t count on it, and better to host somewhere you know will retain the files.