I seams like the Google Home app has an invalid value for '1 Hour' and requests are pilling up.
Google Home is my app #6:
Log entries for app #6:
I haven't tested the other options for polling interval.
Testing with '41 11/60 * * ' gives a very odd result at Crontab.guru - The cron schedule expression generator':
How about '0 * * * '? = "At minute 0.” ?
The method updated() runs when you press Done in the app.
That isn't a true Unix cron, it is Quartz Scheduler cron expression.
That schedule fires every hour, or every 60 minutes (60)
The schedule starts at 11 minutes after the next hour (11)
It fires at second 41 of that minute (11 after the hour)
It looks valid to me... maybe I am missing something.
When you pressed save, it probably built that schedule as a string, based on your current time when you pressed the button, so you pressed it at XX:11:41.
I don't know if that is related at all to your other warnings, though. Warning level logs are usually used to report a possible problem, so it looks like it just queued up a bunch of jobs and it took a minute to clear them out. Do you continue to see this in the logs?
Anyway, you can press the info button for the app, and look for a scheduled job at the bottom of the page for the schedule it was trying to create. If it isn't there I guess it did fail, if it is there you are good. If it is not there it will not poll on the hour schedule you tried to set.
Thanks for your feedback 
Cron job
As a former developer I don't like to see exceptions even that the code is working.
The exception is thrown as a native Java exception, even that it looks right and is functioning something is not quite right/perfect IMHO.
Why does Java throw an exception if everything is in order?
I can see that a scheduler is registered and no more pending requests are logged:
The time that the exception is thrown could be right when I upgraded the unit, so that might be the reason?
Logging
I'm not able to go that long back in time in log entries because the debug log logs to much 
It surprises me that the app is debug logging, because the setting is and has always been set to false:
It doesn't look like this setting is being honored
I can't find a link to the source code.
Is it puiblic available, and I can go have a look?
The source code is not available.
Exceptions are always shown in the logs, even with all logging off.
Warn is not Debug or Info level, so those warning appear to be coded directly so they always show. A conditional bool is usually used for Debug and Info logging, Warn level is its own thing.
You didn't mention if you checked the scheduled job to see if it got scheduled or not. It looks like the exception came from Quartz Scheduler itself.
Thanks for getting back on this.
The image I posted 5 days ago, doesn't that show (at the bottom) that the scheduler was active?
Sorry, I guess I missed that screenshot. If it is working, I wouldn't worry about the error it gave.
Download the Hubitat app
