@s_maheshwaran Ah it’s not a bug. It’s expected behavior.
This is how it works:
- All the sleep enable and disable requests are put into a queue, then executed in order at 6 am and at 12 am.
- All queued users take 40 to 50 min to effectively enable and disable sleep for the last person on the queue.
- If anyone tries it before 6 or after 12 it’s immediate but during the queue processing time at 6 and 12 am it depends on the user’s position in the queue.
Maybe when you put it on sleep during 6 to 12 next time, just see how long it takes for it to go to sleep.