Possible Time Machine and Sentry Bug?

Here is what appears to be a random time machine bug that I encountered. I apologize in advance that I did not capture any images of this happening. Additionally I'm playing the game on Android.
---
Earlier today I was sending a sub ~100 drillers from one of my outposts to another and the time machine initially showed the sub getting to its destination without a problem. However a couple of hours later, before the sub was set to arrive, the time machine started to show show the sub getting shot at by some sentry.
However the time machine was wrong and my sub still got to its destination without any issues.
These outposts I was sending the sub too/from was within my borders and was not within range of enemy sentries to be able to shoot at it. I did have my own sentry traveling to a nearby outpost that would have been within the range of the traveling sub in question but it did not land yet to reestablish its red firing circle before the time machine started showing the phantom sentry attacks.
I'm not exactly sure what happened but because of this it was difficult to schedule future commands for this sub since the future was predicting incorrectly a few hours in advance.
---
Earlier today I was sending a sub ~100 drillers from one of my outposts to another and the time machine initially showed the sub getting to its destination without a problem. However a couple of hours later, before the sub was set to arrive, the time machine started to show show the sub getting shot at by some sentry.
However the time machine was wrong and my sub still got to its destination without any issues.
These outposts I was sending the sub too/from was within my borders and was not within range of enemy sentries to be able to shoot at it. I did have my own sentry traveling to a nearby outpost that would have been within the range of the traveling sub in question but it did not land yet to reestablish its red firing circle before the time machine started showing the phantom sentry attacks.
I'm not exactly sure what happened but because of this it was difficult to schedule future commands for this sub since the future was predicting incorrectly a few hours in advance.