New scheduler (Codename: Ticker) being rolled out

Or the community forum. For the “power users”, this is where we discuss issues, not on social media. Thats the purpose of this forum, to discuss issues, deals, ideas, etc…

If it were to be posted as it was noticed, they could ask the question here, to see how wide spread it is…and then there would be a “show” of concern before all hell breaks loose on the forums because no mention of issue from ST.

Just a thought.

4 Likes

Was the problem fixed from happening again or was the problem just fixed for now as those are likely two very different things?

It’s software. An inexperienced/foolish SW developer/supporter would say, “The problem has been fixed for good”. An experienced/realistic SW developer/supporter would say, “The problem has been fixed” and under her/his breath mutter “Until the next time”.

2 Likes

For a product that you are supposed to be able to set and forget, I don’t understand why the status page doesn’t reflect issues that may only affect some users. All it takes is a “we have recieved multiple reports of an issue (define alleged issue) that may be affecting Some users we are investigating”

“some gaps” is an understatement… I see it all the time on this forum where there are multiple reports of something that isn’t acknowledged by ST. If you get more than 3 tickets in about the same thing, the odds that it’s affecting a bunch of users that Don’t know that it’s affecting them, or are too lazy to submit a ticket are very good.

Like Google, their Apps business puts out emails when .001% of Sheets users have an issue. It’s almost irritating, until I realize how great it is to KNOW there’s a problem even if not affecting my employees.

1 Like

Of course but I asked if they found the root cause and have put a fix in place to avoid it in the future. Just because it’s software doesn’t mean it has to stay broke!

The response I got for my ticket.

Thanks for writing in! I’m sorry to hear that you’re having issues with your routines and modes, and I appreciate your patience.There was an emergency update the other day, so first off, I would recommend an uninstall and reinstall of the SmartThings app.The
issue with Routines and SmartApps not firing could have something to do
with issues on our end that are a top priority for our engineers. I’ll
make sure to let our engineers know what’s going on with your case so
they can look into a deeper cause. We’re actively working to improve on
our platform and apologize for any trouble the Routines and SmartApps
may have been causing you. Once we have a permanent fix in place, we will notify you via email.In
the mean time, you can manually update the schedule on your side. Just
enter the Routine or SmartApp settings and tap Done/Save.If
the Routine and/or SmartApp still isn’t firing as it should, let me
know the email address attached to your account and I’ll see what I can
do from my end.Thanks for your patience with us, and I look forward to hearing from you. Have a great rest of your day!

Ill be sure to post it when I receive their permanent fix email.

Great! I’ll NEVER get to see it. It’s like a cliffhanger that ends with…

Coming soon a Monday near you! ! ! ! ! ! Part two of the permanent fix! Scheduled to soar right after your death, but will probably just be automatically rescheduled!

Jason, I believe this is the thread you were looking for: :wink:

1 Like

I’m going there to complain now

1 Like

It’s a sad state of affairs when your customers know about platform issues before your ops team. And worse when it takes some minimum threshold ticket volume before an issue is detected. I wonder if ST has any sort of real user monitoring or synthetic transactions.

1 Like

Jody I’m a little confused, isn’t the whole point of Ticker to have redundancy to redundancy so that it doesn’t need “corrections”, it’s supposed to keep it functional even when things start to drop off. So is there a fundamental flaw again in the architecture of this new system or was it a coding glitch?
Can you elaborate what the health issue was and what was done to correct it please.

And again it’s showing empty

Scheduled Jobs
None

Whatever was done Jody, it didn’t fix it clearly.

EDIT: the “refresh” to reschedule was done at 1:30 PST so it’s after your time suggested:

Handler Scheduled Time Actual Time Delay (msec) Execution (msec)
initialize 2016-04-26 4:30:00 PM EDT 2016-04-26 4:30:00.264 PM EDT 264 6023

FURTHER EDIT: My spouse is livid cause my kids room is so hot and it’s sleepy time. This isn’t helping my telling her that ST’s got it together.

1 Like

So my sunset routine to turn on my outdoor lights failed to run again - this is two nights in a row. Majorly ticked off at the ticker.

Turn on Front Landscape, etc… at sunset
Label Turn on Front Landscape, etc… at sunset
Installation Type API
Installed Smart App Parent Smart Lighting
Installed Smart App Children
Location Jw Home
Device Children
Virtual Devices
Modes
Date Created 2016-02-06 6:53:03 PM EST
Last Updated 2016-02-06 6:53:41 PM EST
Settings
Name Type Value
action enum on
lights capability.switch Front Landscape, backyard landscape, pergola overhead
overrideLabel bool false
sunriseFollowup false
trigger enum At Sunset
Event Subscriptions
Name Handler Filter Source
sunset triggerHandler true Jw Home (Location)
Application State
None
Scheduled Jobs
None
SmartApp Version Lighting Automation
State COMPLETE
Health HEALTHY
Development App False

Morning rule fired this morning so back on track for me so far.

What’s odd is that there has been a rash of problems reported by community in the last few days. This has been happening for at least a month here…

last night…

With the fix yesterday (26 Apr), last night’s and this morning’s rules were fired off successfully with no issues.

1 Like

ditto for me

all of my delayed events when sent to minutes of delay fail. Seconds look like they work

Lets find out, as of now it’s showing a schedule:

Handler Next Run Time Prev Run Time Status Schedule
initialize 2016-04-27 12:30:00 PM EDT PENDING Once