The five most recent libraries that have been published to your production environment on a Web property are available for later retrieval.
This feature is helpful when you find a bug in your production library and need to rollback to a known good state immediately.
The retrieval process depends on your environment settings at the time the library was originally published. This is important because retrieving an archived library does not change anything on your live site, while retrieving a regular library would.
The following options are available:
Host: Managed by Adobe, Archive: Off: If you are using the Managed by Adobe host and you are not archiving your library, you can republish these older libraries.
Host: Managed by Adobe, Archive: On: If you are using the Managed by Adobe host and you are archiving your library, then you can download these older libraries.
Host: SFTP, Archive: On or Off: If you are using the SFTP host, it is assumed that you have your own archival strategies in place and no retrieval options are available.
Retrieval options for mobile properties are not yet available.
Each Adobe Experience Platform Launch environment provides a link to a Platform Launch library file. Any library that you build in that environment is referenceable with that link.
When you build to a development or staging environment, the old build is cleaned up and the new build is deployed. For your production environment, this link is updated to point to the latest build, but the five most recent builds are kept around before they are cleaned up.
These five most recent builds in your production environment are the ones that are available for retrieval.
When you republish an older library, Platform Launch updates the environment link to point to one of these older builds that hasn’t been cleaned up yet. Platform Launch also issues a purge request to the CDN edge nodes cache to indicate that the library has been updated and a fresh copy should be retrieved from the origin.
This means that when you republish an older library:
No changes are made to any of the resources (or historical revisions) in your Platform Launch property
The way that development and staging environments calculate what is upstream does not change
Consider the scenario when you roll back because of a problem with a specific rule. The rule revision that is now in production might, for example, be three revisions old. When you view that rule in Platform Launch to fix it, it still reflects the latest changes saved rather than what is currently in production.
For this reason, Platform Launch notifies you that a property is in a republished state as a reminder that what you’re seeing in the Platform Launch interface is a little farther removed from Production than usual. This notification is dismissable and appears once per browser session the first time you view the property.
From the Publishing screen:
Downloading an Archived library is more straightforward. You aren’t directly referencing these .zip files anywhere, so you can simply download the older library to your computer and run your usual process.
From the Publishing screen: