Removing the Volo-Stuff does not make any Difference. Jetway does not react when coming back to EDDF!
Of course it doesn't, exactly as I guessed, it's too far to have some effect on EDDF.
Maybe it helps in the Analysis: when the Jetway does not react, the Passenger will also do lengthy Air-Walk - see the attached Screenshot! (I've moved the Jetway with the ATC Menu after it did not react 
)
No need to do that, I looked at your log, and your problem doesn't have anything to do the one at LFPO/LFPG, which causes everything working normally, just the Jetway activates only with the default ATC menu ( unless Voloport is disabled ), and I CAN reproduce this, because it IS caused by the Voloport scenery.
Your problem is completely different, and it shows you have the dreaded error #99, which basically means a Simconnet internal error when we request Jetway data. "Internal error", means it got confused by itself, there are other error codes if we are asking it wrongly.
As I've said in one of the previous post, we could reproduce the error #99 when a scenery had a "ghost" jetway, one with the wrong title that is not available, the Navdata panics and fails the whole call, so GSX reverts into a "slow" mode, asking for all jetways, one by one, so a single failed one won't result in the scenery being reported without jetways.
But your case it's different as well. It's not just one bad jetway that cause Simconnect to panic internally, every single call is failing.
So I tried downloading the VirtualFRA airport, together with the GSX custom profile, went there and, of course, everything works correctly, the scenery doesn't any issue with jetways.
But you said it only happens on arrival. Then I'm afraid the cause might not what you want to hear:
- During the flight, Simconnect got overloaded for any reason, most likely too many objects like AI airplanes, and by the time you landed, it started to act unpredictably.
- Clear proof of this not being related to GSX: you said it's not fixed by restarting Couatl. When something is not fixed by restarting Couatl, you can be sure it has nothing to do with GSX or Couatl, it's just the simulator that went nuts for some reason.
We have been getting multiple reports that, when the maximum number of objects in the sim reach the maximum allowed of 1000, all sort of issues starts to happen, airports disappear, fps might go down, and Simconnect starts to work erratically, and ONLY a restart of the sim can fix it.
