This is a bit of a strange one.
Every few weeks I will notice one or more auto synch loses the 'auto' capability. It basically says the next execution is fine and dandy as well as the last. However it is stuck in some date that has passed. I usually fire up the DeLorean, hit 88 mph, kick start the synch and then come back without losing any data but my Flux Capacitor is getting worn out. I need to get to the bottom of this once and for all. The other issue is the synch does not succeed and it does not fail, which makes the notifications hard to setup to alert you. It just stops happening.
I started noticing it back in Oct 2013 and raised it with Premier Support.
There was an open ticket with other clients as well. The dev team has no idea the cause because the logs did not go back far enough. They just reset the AsyncCommand and it resolved for all clients.
It took only a few days for the problem to return and I raised it again. After a week of lost synch data dev fixed it under the incident SOEP-292. I asked for more details about what caused it other than 'it's been fixed' since now upper management on my side wanted some answers and I have not heard anything back since then from Premier support.
Well guess what - I noticed today that one of our synchs has been stuck since Feb 27.
I am raising this again with support but wanted to put a heads up here to maybe take a peek at your auto synchs.
I have the email notifications set up to alert me of failures but this is not a failure or a success.
I would like to know for other customers what is the normal cadence that you look at your auto synchs?
