Or so seems to be the case. I am using a whole lot of scheduled executions that last as long as the visualelement exists, and when one of them breaks, a random amount of others will so too, which lead me to think that one of them breaking leaves the execution loop making all subsequent ones not execute.
It’s likely we don’t gracefully handle exceptions in scheduled tasks. I don’t think we try/catch wrap them. If you have a setup that reproduces this issue reliably (like, intentionally throwing and having unrelated scheduled items fail) I’d encourage you to submit a bug. Otherwise, wrap problematic scheduled tasks in your own try/catch to avoid the issue.