Notification triggered routine bug One UI 8.0

[MRashid]

After updating to One UI 8.0 Modes and Routines (Ver no. 4.9.04.13) seems to be extremely buggy. Modes and routines doesn't automatically load after your phone boots and only starts if I create a new routine in Modes and routines. Also apparently it is getting killed in the background from time to time being totally unresponsive. 

Also only one notification triggered routine will run at a time so if you have another routine triggered by a different notification from a different app it will terminate the first routines which has no relation to second routine except both are triggered by different notifications. I am very frustrated by the update due to broken Modes and Routines because I was using these routines for years now without experiencing and major issue like this time.

[Gav4b]

Yeah I've noticed that too I've also got a massive battery drain during the night I went to bed with battery saving mode on no app running in the background so it was at 86% when I went to bed at 11:15pm and woke up at 6am and I'm on 3% it's only been doing this since the final release , also if I use you tube music the battery drain super quick and get super hot all other apps are fine , I had a look to see what apps where running and they were android apps for the os ,

[Piper123]

Lots of threads about battery reset already

[Tourbillon De La Vie]

Don't experience any issues. Routines run concurrently etc. When one notification routine cancels the other doesn't the other then cancels it in return when it is triggered. Did you try to wipe phone cache partition

[MRashid]

I wiped cache partition almost a 100 times but nothing fixed. I didn't have this issue in One UI 7 or previous. I am regretting after updating to One UI 8 now. I just restarted the phone and Modes and routines is completely dead now since few hour and nothing works.

They still haven't added a routine action to turn off a mode. I have some custom mode and configured to turn themselves off after fixed amount of time for this reason in the mode duration section. Now after the update it even doesn't turn off after the duration and sayas it is waiting for the notification based routine to turn it off which just ran for an instant in the event of the notification received and can't do anything further. I realized they wrongly categorized notification based condition as a state based rather than an event based trigger causing these errors.