My Garmin suddenly stopped tracking sleep?

It’s the actually sleeping app that doesn’t work

I shouldn’t have to manually input all the times. It’s should do it on its own and describe REM sleep, light and deep

You need to be more specific, I have no idea what exactly is wrong with your data. The HR graph shows around 3 hours of sleep detected on Feb 8, the next screenshot of My Day shows also 3 hours of sleep, the weekly graph shows 3 hr sleep on the last day too, and the last screenshot for weekly averages with the red-circled value shows 8hr24min weekly average, which seem to be quite credible when looking at the weekly data, so I cannot know what you find that is wrong, unless you tell it quite concretely.

Sorry I’m French and I’m trying to explain in a different language. There is no data showing at all. The sleep in My Day (on the first picture) only showed up after I manually inputted the 3hrs. Before I manually inputted the 3hrs the tab didn’t even show in the My Day. There is no record of anything when I look on Connect or Express. I’m not sure how else to explain it. There was just no data nothing describing when I began to sleep to when I woke up all the way to the more details describing which kind of sleep and when you woke up during your sleep. 

i hope it makes sense.

Yes, now it is perfectly clear. Well, I cannot really tell why the watch did not detect the sleep, but shift workers often complain about it here on the forum. Personally, although my sleep patterns are rather irregular, my sleep still either starts or ends in the preselected Sleep Time (watch parameters), and the deetection works flowlessly since the beginning.

I have set my Sleep Time parameters to 22:00 - 10:00 (although I sleep in avg. some 5-7hrs), and the watch does not have problems detecting the sleep even if I go to sleep at 6:30 and wake up at 13:30. If your sleep time varies even more than mine, then perhaps you can set the Sleep Time range even wider - for example from 14:00 to 13:50, hence covering almost the entire day. You could also try 12:00-11:59, or something similar. Not sure whether it helps, but it is worth of trying.

Another possible reason is that the watch simply cannot detect the sleep, because your sleep is not good enough - you may have a sleep disorder. That would not be surprising at a shift worker, at all. In fact it is rather usual. The sleep at people with a sleep disorder is much more difficult to detect without a true polysomnography, availbale only in sleep labs. The watch uses just the accelerometer and the detection of the heart rate variability. Newer models use also the oximetry - but all that cannot really work, if the sleep patterns are seriously disturbed.

I will try changing those parameters like you suggested. I don’t think I have a sleeping disorder (I mean I could very well have one) but before my Garmin I had a Fitbit Charge and it never missed on reading my sleep it also seemed a little more accurate for the “awake” times. I appreciate all your help. I guess now we wait until I go to bed and see if changing the times helped!

I am having the same issue. It used to track my sleep automatically.  The change they did last year or so sucks

 I work different shifts daily,  so setting a sleep time the same time daily  doesn't work. I hope garmin can go back to the old sleep track where it detected your sleep hours automatically 

 I had the original vívoactive and recently bought the Venu.

I actually changed the sleeping times like suggested to. I put it from 00:00 - 23:59 and it seemed to work for last night when I went to bed although I fell asleep on the couch around 22:30 and it didn't register that. It only registered when I woke up and then headed to bed at 00:20hrs. I'm not sure that changing the hours every day is really convenient, but maybe with that new update it kind of forces us (shift workers) to do it that way. I agree it would be nice to change it. Also, does anyone know how to recalibrate my treadmill distance accuracy as I thought it registered in km (as I had it set up) but it was in miles and now it is WAY off!

Same issue