Topics:
Suppression Window (65 Days)
The system uses a 65-day suppression window.
If a communication has already been sent, the system will wait 65 days before it can send that same communication again.
After 65 days, if the conditions are still met (for example, the test due date hasn’t changed), the system will send the communication again and start a new 65-day window.
Example:
If a communication is scheduled 90 days before a test due date, it will generate once at that point. If the assembly hasn’t been tested after 65 days, the system will regenerate the same communication.
Duplicate Suppression by Communication Type
Suppression also works by Communication Type.
If two templates share the same type, they will suppress each other. Cloning a template without changing its type won’t bypass suppression.
Only one template per Communication Type can be published at a time. Publishing a new one with the same type will unpublish the old one.
How to Regenerate a Communication
If you need to send the same communication again before the 65-day window ends:
Create a new Communication Type with a unique label.
Unpublish the template you want to reuse.
Edit the template and assign the new Communication Type.
Publish the template again.
For a small number of records:
Use the existing template to create an ad hoc communication for those records.
Templates don’t need to be set to “ad hoc” to be available for this.
⚠️ Important Notes
To edit the text, subject line, or body of a template, you must create a new template (you can clone the old one).
Avoid changing the Type Label of an existing Communication Type. Doing so updates it for all past communications. Instead, create a new type (e.g., First Notice v2).