If a jobHandle is not found in the session, the engine only emits a log message, but does not remove the job from the session. This leads to orphaned records in the TimerMappingInfo table and can also lead to a duplicate timer getting created in certain circumstances (eg. async nodes).