When an uncaught exception is thrown in a source, I don’t see a way for it to trigger an error workflow (such as sending an email with the exception). This leads to a silently failing source that does not emit events.
I see that workflows offer a default setting to forward to a general error workflow:
@eaptdudfield yes, this is a known gap and something we hope to address seamlessly in the future (e.g. with a UI toggle just like for workflows).
Currently, we expose a stream of events on the $errors channel for every source. These events have roughly the same shape as errors emitted by workflows, so you can forward these errors to your global error workflow (or a different workflow) like so: