Currently when you export a contact list, it appears on the notification page and once complete provides a download link for manually pulling that file OR at that point the file can be accessed by journey automations to export to external sources.
Today, only a single instance of an exported contact list will show up on the notification queue even when multiple DIFFERENT types of exports of that list may have been requested, as I understand due to the rigidity of using the same filename for the list export.
Scenario is this:
Customers have a need to export a large contact list in FULL for reason A, and needs to export a subset of that list (IE just subscribers or just UNsubscribers) for reason B.
Because the same filename is used for both exports, the latest request overwrites the first request.
If we added a timestamp and/or additional detail about the nature of the list export file this should allow for the same list to be exported multiple times in different ways and remain on the notification queue for access.
EG list_export_10_full_20210414050111.csv and list_export_10_unsubs_20210414060333.csv are exports of the same list, but provide different data and remain on the file system for a set period of time before they are wiped.
