Solved! Go to Solution.
I've run into this error with 10.5 as well.
I had a series of layers with joins created before encountering the error. When I unchecked the editor tracking fields the error didn't go away. It wasn't until I removed the joins and joined tables, verified the fields were unchecked, added the join tables, redid the join, and analyzed that the error was gone.
Something seemed to be holding on when I removed the field visibility while the join still existed.
Yes, this time zone feature when pushing ArcPro data to AGOL or Portal is very frustrating. I have two relation tables for my feature class table and all have editor tracking so I can tell when something has been changed in the tables. I tried to define the times as Pacific (a while back - not sure if I defined the time while in ArcMap or Pro) and I thought the transfer process would take those Pacific time zones and convert to UTC. I too, don't need to worry about different time zones since we're all in the same zone. I created a work around by copying my tables and then removing the four editing tracker fields.