I cant' see Richard.ConnectIQ post so  I repeat it:

We have been looking into this issue, but have so far been unable to reproduce what you are experiencing. With a simple watch-app that increments a counter every time it enters and exits sleep the values are always in sync.

FIRST this is no watch-app becouse watch app doesn't have onXXXSleep it's watch face

As it seems to call onEnterSleep and onExitSleep on every wrist gesture. If you do a wrist movement halfway so the device is facing away from you it executes the onEnterSleep function and the screen is black. If you then move your wrist towards you again it executes onExitSleep. Therefore a full wrist gesture of facing away and then back towards you will execute both one after the other each time. 

If you are experiencing something other than this would you be able to provide some code that demonstrates what you are attempting to do?

I've made another test and and my observation was right.

simple code

//global

var gT3=0;

//view

function onExitSleep()
{
        gT3--;

}

function onEnterSleep()
{
        gT3++;

}

function onUpdate(dc)

{

//draw (gT3);

}

wf start: gT3=0 OK

enter sleep: 1 OK

wrist gesture: 0 OK

wait..., sleep: 1 OK

wrist gesture: 0 OK

wrist gesture: -1 NOT OK

wrist gesture: -2 NOT OK

..... -8 NOT OK

wait... sleep -7

so it menas that every wrist gesture calls onExitSleep independed of state watch (in high power) an there is no onEnterSleep call before onExitSleep

I cant' see Richard.ConnectIQ post so  I repeat it:

We have been looking into this issue, but have so far been unable to reproduce what you are experiencing. With a simple watch-app that increments a counter every time it enters and exits sleep the values are always in sync.

FIRST this is no watch-app becouse watch app doesn't have onXXXSleep it's watch face

As it seems to call onEnterSleep and onExitSleep on every wrist gesture. If you do a wrist movement halfway so the device is facing away from you it executes the onEnterSleep function and the screen is black. If you then move your wrist towards you again it executes onExitSleep. Therefore a full wrist gesture of facing away and then back towards you will execute both one after the other each time. 

If you are experiencing something other than this would you be able to provide some code that demonstrates what you are attempting to do?

I've made another test and and my observation was right.

simple code

//global

var gT3=0;

//view

function onExitSleep()
{
        gT3--;

}

function onEnterSleep()
{
        gT3++;

}

function onUpdate(dc)

{

//draw (gT3);

}

wf start: gT3=0 OK

enter sleep: 1 OK

wrist gesture: 0 OK

wait..., sleep: 1 OK

wrist gesture: 0 OK

wrist gesture: -1 NOT OK

wrist gesture: -2 NOT OK

..... -8 NOT OK

wait... sleep -7

so it menas that every wrist gesture calls onExitSleep independed of state watch (in high power) an there is no onEnterSleep call before onExitSleep

I had unintentionally posted a duplicate comment and then removed it. This is still being looked into. 

don't you think that teaching how to use forum in 2021 it's strange? Simple, forum after update is poor, I don't understand why it's not fix - Garmin looks unprofessional and why it doesn't fight for good product.

I probably hate this forum more than anyone else....

There's better options like NodeBB and Discourse, which solve issues this one has with mobile support and navigating long threads, but we're probably stuck with this one forever. You can't even properly quote text unless it's part of the current discussion, and quoting doesn't seem to work in the Bug Reports forum at all.

1. it doesn't run always! Now, I still can't see Richard's reply and didn't see your but was small "reply" which run

2. don't you think that teaching how to use forum in 2021 it's strange? Simple, forum after update is poor, I don't understand why it's not fix - Garmin looks unprofessional and why it doesn't fight for good product. But is not my matter, if Garmin like it, ok.

I cant' see Richard.ConnectIQ post so  I repeat it:

If there's more than 5 comments in a Bug Reports post, you have to click Newest (or Oldest) to see all of them.