How to manage archived items

Eversend allows for ‘archiving’ resources, which essentially hides these items from the UI and prevents them from being used. Archived items can also be restored, once again making them available to accounts inside the current workspace.

This article explains how archiving/restoring items works and details how Eversend treats relationships between archived and unarchived resources.

Various resources inside Eversend ‘depend’ on other resources to function. For example, traffic campaigns require domains to deploy and display campaign templates where traffic is directed. These dependencies can be categorized as follows.

• ‘Upward’ dependencies occur when a resource (Resource 1) cannot operate without another resource (Resource 2). In this case, Resource 1 depends on Resource 2.

• ‘Downward’ dependencies occur when Resource 1 uses Resource 2 but, at the same time, Resource 1 can exist and operate without Resource 2. In this case, Resource 2 depends on Resource 1.

Resources use the following hierarchy to define which dependencies are ‘upward’ and ‘downward’.

In general, resources cannot be archived if they have at least one active ‘downward’ dependency. As an illustration, it will be impossible to archive a domain if it has at least one active traffic campaign linked to it.

'Upward' dependencies

In general, having an active ‘upward’ dependency does not affect archiving. However, it is also impossible to archive templates and/or traffic sources if they are used by an active traffic campaign.

Servers

Active servers cannot be archived regardless of their dependencies. If a user attempts this action, Eversend will display a confirmation window. If the action is confirmed, Eversend will terminate the server and then archive it. Already terminated servers can be archived wtihout restrictions.

Campaigns

Archiving a campaign does not stop traffic or spending on this campaign.

If a resource has archived ‘upward’ dependencies, restoring this resource will also restore these dependencies. This rule applies the entire dependency chain. Consider a traffic campaign with a linked archived domain that has a linked archived API integration. Restoring this campaign will also restore the domain and the API integration.

Campaign resources

Restoring campaigns also restores all ‘downward’ dependencies that are archived.

Note that this does not apply to traffic sources. These resources stay archived, and the newly restored campaign no longer uses their original resource.

Restoration failures

If it is impossible to restore a dependency, the entire restore operation will be blocked.

If a user attempts to restore a campaign whose domain is currently in use by another campaign and/or reserved by another active campaign, it will be impossible to restore the campaign without first making the domain available for use.

To archive an item, perform one of the following actions.

• Right-click on a resource in any grid and then select ‘Archive’ in the context menu.

• Select a resource in any grid and click on the ‘Archive’ button in the quick actions menu.

Depending on the rules detailed above, Eversend will show an additional warning window. In this window, press ‘Archive’ to proceed with archiving the required resource.

To restore an item, proceed to the Archive section in workplace settings. In the central grid, click on the ‘Restore’ button to the right of a resource. Confirm restoration in the modal window to return the resource to the usual Eversend workflow.