No problemo! as some say s*it happens LOL. I wonder if PERHAPS this has to do with the following:
When I was on blocks I shut down my engines, then I turned off the lights, avionics, etc.
Then I proceeded to open the doors (SHIFT+E) at least that was the intention but my fingers tripped and instead of SHIFT+E I pressed CTRL+E (I hate the automatic engine startup) and the engines started spooling up. I closed the fuel valves but to no avail, FS simply goes on its automatic procedure and I had to wait until both engines were started by FS before I could have it accept my fuel valve cutoff command

. As I said that was accidental.
I wonder if perhaps having this "straneous" engine startup when on blocks, after a shutdown and on the destination may have confused the ProPilot analyser.
Anyway, it might give you guys some light into the probable causes as what happened to me is also very rare (and unfortunate combination of keys).