Portcast’s Web App has a container auto-archiving feature that can be helpful for some customers. Read on in order to understand if it fits your workflow, understand how it works and avoid accidental archiving.
To activate or de-activate auto-archiving, head to the Portcast Web App and, under your username, on the left sidebar of the app, choose Org settings:
You will be taken to the settings page for your Org. Here, on the top right, you can access a toggle button for activating and de-activating container auto-archiving:
Upon activation, you can also set the number of days after which auto archiving of containers should take place.
The auto-archiving of a container starts being calculated once the refresh status code of the container has been marked as NOT_REFRESHING (learn more about container statuses on the dedicated documentation page), meaning the container has completed it's tracking lifecycle and we don't expect any more container events to be populated.
This marks the beginning of the calculation; once the number of days set in the Org’s setting, as per above, the container is auto-archived.
Note that, upon activation of auto-archival in the Org settings, the system will look back 30 days into your system and auto-archive any container that matches the rule above, meaning any container whose refresh status code has been NOT_REFRESHING for more than the number of days the user has input will be auto-archived.