- Posted on
Sun Sep 06, 2015 9:51 am
-
jay (support)
offline
- Site Admin
-
- Posts: 18220
- Joined: Mar 19, 2008
- Location: Austin, Texas
-
That's extremely unlikely - actions are executed in separate threads from those that process schedules and those that receive incoming events from the various protocols. We specifically architected the system so that there are no bottlenecks like that.
What errors/log entries are showing up in the Event Log when one of these schedules fails to execute? How do you know that the schedule isn't executing? Do those schedules have any conditions that may be stopping them from executing? What specific actions is the schedule that's not running executing, and are you sure the actions themselves aren't what's failing (due to protocol issues)?