I have to come back to this, since the same problems occurs three times in the raw, and these are all three complete nights when I used my new AM5 so far. I think I'm going to stop using AM5 until some clarity comes.
I started this thread with this problem. I then updated the mount software to 1.1.2 as advised and used the mount with the public beta of ASIAIR 2.0. The shift happened in the same pattern as the first time. This time twice though, where as I was the witness of the first time. I saw that a GoTo dialog briefly popped shooting of a sub was running. I quickly clicked on cancel, but it did not help: the sub was already shifted. I did a go-to the target and resumed the Autorun. Later in the night I went sleeping and the mount shifted the target again once in the night. I had to delete around 1/4 of the subs. I was not able to submit a bug report, since the 2.0 beta requires a ZWO account for this, but I was not able to create one since the "Next" in the registration form was blocked even though I entered a valid address and agreed with terms of service.
Last night, the same problems occurred again and I had to delete 1/3 of the subs. This time I reverted the public beta 2.0 to the released 1.9 version, but this did not make any difference. The mount software version remained the same: 1.1.2. The hand controller was not connected in all cases.
And no, the problem was not caused by lost star in guiding. I checked the guiding log, @Sam@ZWO . The shift occurred at another time where as guiding lost star much later.
I can provide samples of the subs and some logs if someone tells me where to copy them from, @tech@zwo I did not summit feedback since I did not know that I have a problem as I turned the mount off while rigging down. BTW, I once asked in one of my beta feedback to enable persistent storage of logs sorted by date so that a user can submit a log for a session even after ASIAIR was once turned off.