Pending Export not detected on Autosync Startup

[khandelwalpiyush]

1. Installed latest v1.1.6500

2. Before starting that I can see pending exports in an ECMA CS (ACMA)

3. Expected autosync to kick of exports but didn't happen

Autosync Log since startup

autosync.log

[khandelwalpiyush]

Unable to reproduce this issue..

autosync.log

[khandelwalpiyush]

Actually I saw this again in our production environment today with LDS and FIMService having pending exports.. Trace was not running and running the older version v1.0.6487

autosync-prod-notrace.log

Doing the trace and repoened the GUI and then it did the EALL of LDS and FIMService
as expected.. Same behaviour as before. Not sure if there is any co-relation betweeen the GUI beeing recycled or service itself restarted to enable Trace is flushing out the error

autosync-trace.log

[ryannewington]

Can i get a trace from the latest build, with the issue occuring after stopping the controller, then restarting it?

[khandelwalpiyush]

Attached.. So I enabled trace and had to restart service.. thus the first few runs will detect EALL ACMA.. But then I stopped controllers and did a DIDS on FIMService.. Started contollers and I expected a EALL ACMA but just did a DS FIMService and did nothing.. then did a DI on other MA's as expected..

autosync-controllerrestart.log

[ryannewington]

Is this still an issue in latest builds?

[khandelwalpiyush]

Exact steps in #116 (comment) are reproducible in v1.1.6582.2440

autosync-trace.log

[ryannewington]

Notes for myself. The root cause of this issue is that the routine to detect unmanaged changes has the following check in it

if (run == null || this.lastRunNumber == run.RunNumber)
{
   return;
}

On a fresh boot, the run variable is null, so the function continues.

However, when stopping and starting the controller, it looks only at the last run number it saw on the MA. this will be correct that the controller has not seen any runs while it was stopped.

However, in the example of staged exports, they were caused by a sync run on a different MA. This condition is not taken into account by the check above.

[ryannewington]

@khandelwalpiyush here is a build to test

autosync.zip

[khandelwalpiyush]

Fixed in v1.1.6597.29054