Error handling of automations

[fsbraun]

I'm always frustrated when an automation stops with an error which needs debugging.

• Configurable way to handle errors, e.g., mailing a traceback to admins.
• A view that allows only inspection of automations which stopped after creating an error.

I am planning to work on a solution soon. Input, however, is strongly welcome!

[jacklinke]

Ooh, good stuff. I'll think through this as well and update with any thoughts.

[fsbraun]

For the first item: Just having started looking at it the obvious and simple solution might be using a logger.exception call which can be configured freely, e.g., send an email to admins or whatever. Also, the emails can include the traceback. What do you think?