This is a known issue with the latest production release (build 1480). There is a fix for it in Early Access (build 1484) which will, hopefully, go to release in the next day or two.
See the thread below which started discussing the prior Early Access build (which exhibited the issue) and goes on to describe the same issue in the production 1480 build and the solution, hopefully, in the 1484 build Early Access build: