Certificate creation date vs. activity completion date
When a certificate is triggered after completing an activity in Control, the creation date of the certificate is always set to the current date. This happens even if the activity’s completion date is manually set to a date in the past. As a result:
The PDF certificate can show the correct completion date if the automation includes that field.
The user profile will always display the creation date of the certificate, not the manually chosen completion date.
How expiry dates are calculated
The expiry date for a certificate is calculated from the creation date, not the activity’s completion date.
For example, if a certificate is created on April 11 and the automation defines an expiry of 365 days, the certificate will expire on April 11 of the following year. This applies even if the activity was completed earlier.
🔍 Note
This behaviour is due to how the UserCertificate object is designed. It stores the moment the certificate is created, not the completed date from the module or invite.