Gmail draft formatting lost between desktop & android versions

[ArtofK]

Hi Everyone - I hope this question is in the appropriate forum...

-I drafted an email on Gmail for Android (all apps uptodate) (Let's call this Draft 1.0)

-I edited the email some a later (Draft 1.1)  to add bullet point formatting and more non-formatted text on Gmail via Chrome browser on Desktop (PC - Win 10)

-The draft saved - and I even made a minor edit several hours later which also saved (Draft 1.2) (also Desktop)
-I opened the draft on my Gmail android app to add a few more pieces of text and found that the draft available was reset to Version 1.0!!! All formatted and non formatted text done since has been lost.
-Opening the draft on Desktop now also shows Version 1.0.

Is there any way to prevent this from happening? 
At least a warning message saying that "This draft cannot be displayed on the Gmail android app - opening it will cause any changes made outside the app to be lost" would be useful at the very least...

All Apps are up to date.

[KAM]

@ArtofK One thought, I haven't tested your scenario but I have seen issues where if I am working on multiple machines, the Drafts sync takes a while.  Can you try making a change and wait a good 15 minutes before checking on the other machine? -KAM

[ArtofK]

I'm so sorry but this is the first time I'm seeing this message - 11 months on! Thank you so much for taking the time to reply!

[bill_pier3]

I have seen similar, but I think the problem is web Gmail service. I found it reliable when I adopted the practice of refreshing the Drafts email list before editing an email.  This ensures that Drafts from the mobile app are synced before editing.  The Sync to/from the mobile app and the web service are almost instantaneous - so there's no delay; the issue is not with the edits being synced, but rather with the web service not having the latest version when an edit session starts.

[ArtofK]

I'm so sorry but this is the first time I'm seeing this message - 11 months on! Thank you so much for taking the time to reply. I think this might have been the issue too...