The above error occasionally appears in the Worker Process (WP) logs at the time when the Activity is triggered but does not start. This is encountered as a result of a scheduling error due to a RunID conflict with old statistics data. This may also occur when there has been a RunID turnover* at some point in the past.
Some of the scheduled activities get stuck in a status of “in generating” or other inactive statuses.
*RunID Turnover: The last possible sequence number has been reached and the RunID sequence starts again from the lowest possible number.
The RunID turnover itself causes no impact on the workload processing and it’s normal for environments existing for longer period of time or processing lots of Jobs.