Has anyone had issues with the Timestamp field on the Siebel IT Resource not being updated after an

My understanding is that when a Siebel Recon job is finished, that the Timestamp of the associated Siebel IT Resource record is updated to match the Last Run Start of the Job. 

In this way, jobs are incremental and the updated Timstamp value is then passed to Siebel via the Siebel-OIM connector on the next Recon job, where it forms part of the searchspec on the appropriate BC.

We are not seeing this, so our jobs slowly take longer and longer, until such time as we manually update the Timestamp to a more current date/tiem.