There is a known bug in OH right now where Rules start executing before everything else in OH is loaded and available. I’ve even seen it complain about stuff like global vals and ON not being defined. There is an issue open.
try/catch inside of Rules can’t catch everything that can go wrong because some exceptions occur in the underlying Rules interpreter kill the Rule so thoroughly as there is no Rule left to roll back down the stack trace. In short, the Rule is gone so the catch is gone so there is nothing there to catch the exception.
This is not true for all errors. It is mainly a problem with type errors and trying to call Actions that don’t exist.
See Cleaning up the startup process / renaming rules (windows possible) for a workaround to address the root cause of the error in this case.
Beyond that, you can schedule the calls to the Actions to occur 30 seconds or so after startup. By that point everything should have settled.