2.3.2 will have a limiter on the number of recurring jobs that an app/driver can schedule 
6 Likes
Will there be some loud indication that said limit has been reached?
Chances are the guilty culprits are accidental mistakes and likely the result of them not being scheduled would be a rather unnoticed failure of things to behave as expected--without clear indications about why unless there's some sort of notice (e.g., one that lights of the notification flag in the upper-right corner like hub updates do).
Yeah, schedule() call will generate a runtime exception that will appear in the logs.
The limit is going to be pretty high, I'm thinking of 30, just to pick a number. It is meant to catch runaway logic, not limit app/driver functionality.
1 Like
Is there a way to pop the "flag" icon on the GUI when that message occurs?
Perhaps it would be cool to be able to create (regedit) filters on the logs that could be used to trigger that flag and/or send email notifications??
Or is there a better way to et active notifications when stuff happens (so you don't have to pour through the logs manually)??
