Timer error messages

[rossko57]

@danst

where I should look (beside the timers)

Good start.
It does show you a “skeleton” of the timer code, so you.d look for one that begins with -

logInfo(xx,xx)
if ( ) {
 xxx
}
logInfo(xx,xx)
xx.sendCommand(xx)
xx.sendCommand(xx)
xx.sendCommand(xx)
xx

which should be fairly distinctive.
It’s probably blown up on that third sendCommand, trying to make a command from something that isn’t available.

Before diving in too deep, if you have long-running timers and if you have been editing rules files - beware orphan timers.

[SOLVED] Unhandled Exception w/o active rules

That looks like the sort of report you get from orphaned Timers - typically, a long running timer was spawned by a rule, and the rule file was later edited on other business. When the rule file reloads, the context for the waiting timer is destroyed - but the quartz scheduled timer job is not. Maybe hours later, the now “orphaned” timer code executes and usually fails with a NullPointerException because some variable it references no longer exists.