bamarayne
(Jason "The Enabler" as deemed so by @Smart)
122
ALL THINGS OPERATIONAL
Imagine that! Was a lesson learned? It sure doesn’t seem to be that way.
Automatons aren’t failing. They just aren’t firing at all! I guess if they don’t fire, than they can’t possibly fail. Which means you can post this for the world to see. …
I wonder if the root cause for this one is the same as the melt down in march. You remember, that’s the one that was caused by. … what was it again. …oh yeah, it was. … wait. … ummmm… yeah. … I’m pretty sure we were told what it was. … right. … we were told. … chirp, chirp, chirp.
Had issues this morning. 2 Hue Bulbs turned on at 5:25am like they were supposed to. At 6:00 they are supposed turn off… This morning they didn’t turn off. Had to manually turn them off. All local automations ran as scheduled.
Hey, they thought you were too happy last week with your system, so they sent you a reminder that we are not out of the woods, just yet. Or as @JDRoberts put it, some may forget that reliabily is still a big issue…
just reviewing job history for other scheduled events, the delays and execution times are all over the map.
Delays ranging from 14ms to 50s and exec times from 170ms to 40s, and that was just one app…
We discovered an issue that was impacting some schedules and have corrected it. If you are currently having issues with schedules, PM me or send a note to support@smartthings.com.
Thanks @jody.albritton. However, if you got a note about this, then clearly you guys were aware there was an issue yet nothing was posted to status.smartthings.com nor via email.
I can confirm the fix worked for me for my rule that had a delayed power off after 5 mins… kept failing over and over today… just tested and it worked. I turn on a virtual switch after a door is opened and then do a delayed turn off (5 mins) as part of the same actions and it worked. Thank you!
I had seen some isolated reports of schedules failing starting late last night, but this issue was not impacting everyone. It was only after reports increased about an hour ago that we discovered the issue and steps were taken to correct the scheduler health. The status page will only change when there are platform wide outages/service disruptions. I realize that this leaves some gaps in information dissemination and we are working on our processes to address that.
I highly recommend using something like Facebook or Twitter for smaller issues that are still under investigation. It’s quick and easy and can reach many followers.