Invalid Current handler value after trading between games?

[Jacinthe]

I injected an XYZ shiny Xerneas WC into my OR save and redeemed it. Then I traded it to Y to get the Kalos ribbon and finally traded it to AS.

 

Since I made save backups of each step, I checked them in PKHeX. Everything's fine in OR and AS, but in Y I get the error "Invalid: Invalid Current handler value, trainer details for save file expected another value. Invalid: Current handler cannot be the OT." I didn't edit Xerneas in PKHeX whatsoever and only did some normal trades between games, then how come it gets flagged as having an invalid current handler in Y?

 

In case it's relevant, for every save file, the information shown in the OT/Misc tab was:

Current Handler: HT

Latest (not OT) Handler

OT: Name of the save file the Pokemon was in 

 

Another detail that might be important is that my OR and AS save files have the same trainer name, but obviously different and naturally generated TID and SID, but Y's trainer name is different.

 

It puzzles me that:

1. There were no problems with the current handler or anything else in the game Xerneas got redeemed (OR).

2. Then the 'problem' popped up after a normal trade to Y and the Xerneas getting the Kalos ribbon.

3. After being traded to a third game (AS), the alleged problem simply disappeared.

 

I thought that if the mon was properly injected and then just traded normally, there would be no issues. But now this raises two questions:

1. Why does the 'error' only get flagged when reading data from the Y save file? Is there a real legality issue or is the error in PKHeX's reading or data analysis?

2. In case there truly is a real legality issue after Xerneas was sent to Y, does the fact it doesn't get flagged anymore in AS mean that the problem got solved or did any part of its data got 'tainted' and now it's no longer 100% legal? Does the game data track the chain of past handlers in a way that the previous invalid handler information is stored somewhere in the pokemon's data and could be detected and shown was illegal (even though it really wasn't for all I did was a normal in-game trade)?

 

Thanks in advance!

 

EDIT: Noticed something really weird. Before the error messag popped up in Y, I had checked the pokemon's memories. Now I reopened the save file in Y and noticed that Xerneas doesn't get flagged as having an invalid current handler if I don't open the memories tab. I tried in AS and the same thing happens: pokemon 100% legal when checked and having invalid current handler after checking the memories window. I'm not editting any memories nor anything else, just looking at the memories and then closing the window. So now it seems to me even more it's just some PKHeX error, but I wonder why it gets triggered by simply opening the memories window and if it has any legality implications for the mon.

I checked the memories in-game and the text is the same as shown in PKHeX, so I really don't see why this would trigger an error, especially since it doesn't show any before opening the memories window.

 

EDIT 2: Tried checking other Pokemon and noticed this happens to any event or traded Pokemon, that is, if I'm not the OT, a pokemon will get flagged with having an invalid current handler AFTER I open the memories window, even though it was shown as 100% legal a couple of seconds earlier.

Edited 49 minutes ago by Jacinthe
Adding relevant information