I hope this is still the only case when it shows, but it is doubtful (today) given the amount of pings showing in history.The only reason cancelled trips don't show on your log is because the unique trip ID of the request got picked up by another driver and ends up on their log because they were the last driver that had it. When you cancel and the request doesn't get picked up by another driver the unique trip ID ends up on your log because you were the last driver that had it.
It would depend on how they setup the SQL database, but it's very unlikely that a unique trip ID could be tied to two drivers simultaneously.I hope this is still the only case when it shows, but it is doubtful (today) given the amount of pings showing in history.
Don't sweat it just yet. It seems that happened to me and I had another well over 90% acceptance while ACRO about 75% this last week.much less. I can almost do it with my eyes closed