This ticket is an architectural discussion continuation of the bug described in the bug workaround created in
Steps to reproduce:
reference episode catalog process issue from
It is unclear to the adopter if temporary and permanent artifacts are both being saved to the Asset Manager during processing and scheduling are at what being tagged for permanent storage. The confusion is leading to everything coming out of the asset manager being tagged for archive when the element is not intended to be permanent.
It is clear which elements from the Asset Manager snapshot are intended for permanent storage and which are temporary persisted to aid processing. Or, if there is another persistent storage architecture for managing assets that are working artifacts and not intended for permanent reuse. The local requirements can be configured through the workflow and not hidden inside the Java code. The archive strategy options are documented or described in a ticket somewhere for the community.
Workaround (if any):