Yes, I too am having issues once again just for normal timed events (set for static times throughout the day).
I logged into the IDE today to “update” all of my routines so we will see if that helps as it has in the past.
I just got into this again after a few months being away. I have been trying to get to the bottom of the various things that don’t work right in Smartthings. It seems that in my case it is the sunrise/sunset stuff that does not work. I use sunrise/sunset in goodmorning and goodnight - they don’t execute at all. I use the canned Smart lighting app to turn a switch on/off at sunset/sunrise. This usually works, but I noticed last night at 1:39am it turned off/on twice in the same minute. I use the “No Body Home” Smart App for presence to control modes. The presence detection for Away was/is great, but figuring out which mode on return is based on sunrise/sunset and is marginally ok. I keep asking myself - When do I throw in the towel on Smartthings?
Can you shoot a note over to support - I am not aware of any trending issues and we can help investigate.
I’m also having routines partially executing for the last week or so since the last update. I sent a note to support, haven’t heard anything back.
Nothing changed on my end, but now Good Night, Good Morning, I’m Back and Goodbye are not executing at all - or more often - partially executing.
Any ideas?
What worked for me in the past was deleting the routine and rebuilding it.
I tried making a new Routine that would accomplish the same thing - but it gets the same results. Runs partially, gives me an error.
Do you think it’s essential that I delete the existing Routine first?
I guess I don’t have much to lose at this point, as I still haven’t heard anything at all back from Support.
you could also move your routine to webcore.
Have you looked at Live Logging in the IDE while the routine executes? Maybe an error is being thrown during the routine preventing it from finishing. Also there are sandbox timers on routines and all other smartapps - a 40 second total time for the app to run and a 20 second total time for any individual function to run. I have definetly seen routines not finishing all the way because of a single cloud device that timed out while attempting to communicate with another platform or when a user has hundreds of devices selected for an individual routine. In that case maybe multiple routines could help your situation. Either way I think it’s worth taking a look - if you do see any errors please post them here (as long as it has no personal information in it - if it does please DM me) and I can take a look.
Talked to support and tried a few things and figured out the problem last night.
Turns out my Arlo cams being armed via Routines were causing my issues. Took them off of each Routine and they work fine again. I’m hoping that gets straightened out, but for now I’m going to use IFTTT or perhaps Webcore to arm the cams on ST mode.
I also have a ticket into support as my standard routines are not executing the defined actions. Only thing I can see on my end is that the event log show execution times that are significantly shorter than before, perhaps indicating an error, but I cannot see why, since they only have switches and SHM to turn /on/off at sunrise/sunset.
Just had this happen (built-in routine failing to execute fully) this morning.
I first was having problems with the “i’m Back” routine not disarming SHM, so I created my own routines to handle the disarm/arm of the system. This morning, my partner went to open the back door and the alarm went off, looked back over the logs and saw the Good a morning routine executed (and said it changed the mode and SHM), however all it had done was change the mode, SHM was still “Arm (Home)”.
I’ve fixed this now by creating my own Security (Good Morning) routine, but I wish smartthings would fix the underlying issue!
I’m not sure what is happening with my existing routines, but in the last 7-10 days, my existing routines are firing per time schedule, as seen below, but NONE of the actions within the routine are being executed, for example: change mode, turn on switches, lock doors, SHM, etc.
Did I see that deleting “Good Morning” and “Good Night” and all other custom routines and redefining them was a solution. I need confirmation before doing this radical procedure. I created a new routine and it executed the commands within the routine.
I should also add that when I have WebCore execute a routine, like “Good Morning”, it performs as expected.
Ugh!
Same thing happening to me. Before I found this thread I created this
https://community.smartthings.com/t/why-isn-t-the-automation-triggeringI’ve been having similar issues with not only routines but also Automations not working intermittently. I raised a ticket with support which got escalated to second line (but not before they’d had me delete most of my automations and 3rd party SmartApps “because they sometimes cause problems”) who I presumed had done something to kick everything back into life about 12 hours later. However the problems continued until this weekend when everything stopped working again for about 12 hours. When I updated the ticket with the latest issues I got the following response:
“I’ve had another look into this for you and I noticed that sunset and sunrise were missing from your Weather Station (part of the Routines system). I’ve pushed an update through on this for you, and it appears to be back to normal. Please do let me know if this kicks your Routines back into action!”
When I asked if this was the cause of my problems I got this follow up:
“It does appear to be directly related to the Weather Station issue I’d spotted. I have had a couple of other users that experienced similar issues to yourself around the same time and my update got them back on track. You shouldn’t have any issue going forward recreating all your Routines and Automations, but we are here to help if needed.”
I’m not convinced as “I’m Back” failed to fire when I got home this evening. I’ll test again tomorrow as its dark, cold and wet outside now.
ETA; I have tried deleting and recreating the routines and automations with zero effect and also see that the logs tell me that mode has changed when it hasn’t.
Similar issue with shm status not changed by routines last 2 days, no news from support so far
My routines haven’t been working for the past month or so and Ive been back and forth with their support and have gone nowhere so I gave up. My routines would trigger but my thermostat wont change to the desired values. It doesn’t happen all the time but id say it happens 80 percent of the time.
I suggest that you or anyone else noticing Routines (or any automation) that is not completing check the hub event log in the IDE for clues.
One specific thing to be on the lookout for is to check if the following events have been logged within 10-20 seconds after the routine (or automation) was triggered.
2018-02-21 8:59:28.446 AM EST
5 hours ago HUB hubStatus zw_radio_on
2018-02-21 8:59:28.441 AM EST
5 hours ago HUB hubStatus zb_radio_on
The presence of these messages in an indicator that something went wrong with the hub while it was processing the commands to devices. If those messages are not present, then it could also be possible that the routines are simply timing out after 20 seconds, possibly due a slow device, like blocking synchronous network call to a cloud device.
But is anyone sees those specific messages logged right after a routine or automation has been run, it’s a very clear indication that something went wrong
I also created a very simple SmartApp to send me a push notification anytime these events occur. Sadly, this human automation is necessary because I cannot currently trust SmartThings to turn the lights of, or the doors locked.
There is definitely something going on over the last week with Routines:
I have Routines that do multiple things when leaving:
Armed / Away
Mode to Away
Lock door
When I leave, everything above works with exception to the lock locking. I have had this in place for over a year. I have LANNouncer on my phone and it tells me that it’s Armed / Away and the mode changes correctly. However if I wait a minute, the lock never locks. If I manually lock it from Things it’s fine. So it’s not the lock not communicating with ST.
So I come home and the other routine that Disarms, Home, opens garage door and unlock works, except that it take about 30 seconds for the inside lock to unlock.
Now if I leave again, this time the Routine successfully locks the lock.
There is definitely something happening or that changed on the backend.
I went as far as removing the original Routines and creating new Routines to replace them based on others issues reported.
3/4 of the Routines execute sometimes and other times they work completely and then also major delays happening in between sometimes.
It’s not my environment or my mesh or the device not communicating.
Check your hub logs as I suggested. This is something that has been going on for several weeks, at least for me.
I did and stopped bothering with it. At first I thought it was my lock causing all the issues and reset the entire lock, removed it from the SmartApp, yada yada yada. You know the drill. 
That’s when I realized it was a “it’s not me, it’s you” situation. It’s a nuance that will eventually go away or be made worse by additional changes. Hehe.
I just wanted to report mine so that others don’t think they are going crazy and losing their minds.
And FYI Steve, the lock is Z-Wave so probably right in line with your issue and logging.
It’s the only device in the set of Arm Away/ Arm Home / Disarm Routines that has an issue. It’s never the MyQ Garage door or any of the lights within the Routine, just the lock and the issue doesn’t happen everytime the Routines run. Sometimes it’s 100% successful, sometimes it just doesn’t perform the lock and unlock, and sometimes there is a one minute delay in performing that portion of the Routine. Bizarre I tell ya.
I know at the end of last year, the UK had all sorts of issues with the Mode being ignored for all of their Routines and then also people having Routines tied to Sunset and Sunrise and those failing because their profile location did not contain those values.
I’ve learned that when these things are going on, I just don’t mess with them or try to make it worse.