Resource expiration

Nothing expires on its own. Setting the date marks the resource; the Expire Resources rule is what finds it afterward and acts on it, and both the rule and its action are disabled by default. Servers expire through their own mechanism, described in Server expiration.

Set an expiration date

Provide a value for the Expiration Date parameter. There are two ways to do it:

• At order time, by adding Expiration Date to the blueprint as a blueprint-level parameter, with its destination set to the resource, so the person ordering can pick a date.
• On an existing resource, from its Parameters tab.

Act on expired resources

The Expire Resources rule pairs a condition that finds expired resources with an action that acts on them. Both halves are disabled by default, so enable the rule and its action before relying on it. See Rules for how rules are enabled and run, including the recurring job they depend on, which is also disabled on a new instance.

The Find Expired Resources condition only identifies resources whose Expiration Date has passed. It does nothing to them, so the behavior you want lives in the action.

The Send Email About or Delete Expired Resources action treats a resource in one of two ways, according to its Threshold Days Expired input, which ships set to 30. While a resource has been expired for fewer days than the threshold, each run sends its owner a warning email. Once it has been expired for at least that many days, the action deletes it and emails the owner. Use it as it is, change the threshold, edit the action, or replace it with your own. A rule can have more than one action, so notifying and deleting can be split.