It was fixed it seems in the prior developer beta but is back after installing beta 8 today the workaround noted above works at least in the short term

Noticed the same here on two different watches - tried Beta 2 today but still not back...