Who is this article for?

Users who receive expiration notifications for Documents without an expiration date.

Test environment access is required.

This article outlines the cause and solution for issues with incorrect expiration notifications being sent out.

1. Issue

You might notice that a Document triggers an expiration notification even though it doesn’t have an expiration date set.  

These emails might be sent from the Test environment instead of the Production environment. The Test environment could have a similar database copy as the Production environment, containing the same Documents with active expiry settings.

2. Solution

To resolve this, check if the emails are being sent from the Test environment.

Test emails and Production emails now come from the same email address. Ensure to differentiate between them by renaming the [FromAddress] email address to differentiate between Production and Test emails.

If the Documents for which you receive incorrect expiration notifications are not present in the Test environment, or if the email address for Test is different and you confirm that emails are coming from the Production site, reach out to our Support team, including the Document ID and screenshot of the email notification.