We were able to reproduce this behavior.
Automation Engine: 21.0.9.HF1
Agents 21.0.9 with the name UNIX01 and UNIX02
UNIX01
20240213/131528.376 - U02000308 Agent certificate file './security/UNIX01.cert' was loaded, expiration date '20240214/125130'.
20240213/131528.387 - U02000308 Agent certificate file './security/UNIX01_ca.pem' was loaded, expiration date '20440207/122453'.
20240213/131528.387 - U02000296 Agent certificate has been expired, requesting new one.
UNIX02
20240213/131401.153 - U02000308 Agent certificate file './security/UNIX02.cert' was loaded, expiration date '20240214/130307'.
20240213/131401.154 - U02000308 Agent certificate file './security/UNIX02_ca.pem' was loaded, expiration date '20440207/122453'.
20240213/131401.155 - U02000296 Agent certificate has been expired, requesting new one.
As we can see both the agents expiry date was 20240214 but it was reported to be expired on 20240213
Automation Engine: 21.0.9.HF1
Agents 21.0.9
The agents have a check that takes place once a day and if a certificate if about to expire (in LT 2 DAYS) the agent will request a new one.
The U02000296 Agent certificate has been expired, requesting new one is a general message which is used anytime a certificate is renewed either that is expired or close to expiry.
The same message is used in any situation a certificate is renewed, and its initiated on Agent side. As these are informational messages only, and the use of certificates is transparent for the user - no interaction is needed - all works automatically, message is still correct.