The document-creation workflow node gets a new "Overwrite existing file" switch. When it's on, a regenerated file — say, a per-company report your workflow rebuilds every night — replaces the earlier file with the same name in your workspace instead of piling up a new copy on every run.
Previously nothing cleaned up the old versions, so a workflow regenerating a thousand documents left a thousand stale copies behind each run. With overwrite on, the new file is uploaded first and only then are the old same-named copies removed, including detaching them from any tickets they were attached to — so the filename always points at something, and your tickets only carry the current version. The sweep also picks up stale copies left behind by earlier runs, so historical clutter cleans itself up the first time you run with overwrite enabled.
Matching is by resolved filename within the workspace, so make your filename template unique per record — for example by including an external ID. Note that a replaced file gets a fresh link each run; downstream steps should take the link from the node's output rather than hard-coding it. If cleanup ever hits a snag, the new file is kept and the run still succeeds.
Off by default — flip the switch on any document-creation node to opt in.