Repository navigation
More optimal way to cleanup/delete blob from external storage, with tradeoff #146
Description
Currently the blobs are only deleted after the whole workflow's history are deleted (all runs -- including runs from continueAsNew, reset and IDReusePolicy).
This is the safest way, mainly because Temporal/Dex support "Reset/TimeTravel" API to go back to any previous point of the history.
But this could potentially lead to some extra storage cost that user may want to optimize.
E.g. if user can accept that they won't reset to any point before X days ago, then we can delete the blobs more aggresively -- we could find the closed runs that closed more than X days ago, if any of the blobs are no longer be used in next run, then they can be safely deleted.
Activity
longquanzheng commentedon Nov 9, 2026
The Go blob model was removed with the Go Server (#1059). server-zd deletes superseded values and old history by window and purges objects with the run. Closing; open a new issue for a configurable retention if needed.