Developer forum

Actually after some more testing the LastRun in v9.15.4 does not work either, but this time it is not updated at all. So just stays at an older date/time.

I just ended up writing my own function to make sure this works for my custom integration task on any version. But this will probably also be an issue for any "Delta" replication task using standard integration modules.

Hi Jon,

Yes we set the SetLastRun() before running the job, as we don't know how long the job takes to run, and we do this because when doing "Delta" and set the time after the job will conflict with what data you'll recieve from e.g. your endpoint, so all the data that has been updated on the external system, while the job is running, will not come in the next "Delta" run.

The "Old" logic, before we implemented this, it was looping all your log-files to check for a specific string-line containing "Batch succeeded." and that is wrong, as this is the last line of the log-file, meaning it is after the job is finished, so this could not be used for "Delta" jobs.

I think there is a bug in the version 9.15.4 for the new logic.

BR

Matthias Sort

Hi Matthias,

Ok. I can see now how the "Delta" works as you call the check for LastSuccessfulRun when you create the source object, before you call the initialise or run the job. If I want to use this the last successful run in the RunJob function I will have to make my own implementation of this.

Regards,

Jon.