When a combination of agent group with "Next listed", Generate at activation on a job, and no agents available for hostgroup is used, the activation time shows the time the agent starts rather than when the task was originally activated.
Expected behavior: job starts running when agent connects and activation time stays as seen in #7 timestamp above
Actual behavior: job starts running when agent connects and activation time is set to same time
Release : 12.3.8
Component : AUTOMATION ENGINE
This behavior is as designed. The documentation here has been updated to include the note "Agent Group is resolved. *NOTE: if Agent Group is unable to be resolved due to no agents available and Generation at Activation is set on a job, Activation timestamp will update to the moment it can be resolved.*"
If the original activation time is needed, the RH table can be used, looking for the original RH_Timestamp1 for the runid (RH_AH_IDNR)