tap> is a core function, so if its argument fails to evaluate, tap> is never called and Portal never receives the value.

You could use something like https://cljdoc.org/d/djblue/portal/0.35.1/doc/guides/logging/portal-console if you would like a macro that catches exceptions in its argument

No worries, I lost no time in simply looking in my REPL 😃 good to know about log thanks!

The https://cljdoc.org/d/djblue/portal/0.35.1/doc/guides/nrepl middleware will also automatically tap eval results / exceptions as well 👌