When throwing an exception in a transaction function as per the docs the transaction is rolled back as expected, but no exception is logged or thrown back to the caller so there is no way to know that the transaction failed, and what the actual exception was (that I can see)
Is there a way, perhaps something similar to this v1 workaround that could be used in v2?
Hi @wkok for v2 see the xt$txs table for this information, mentioned briefly here. Currently the level of information exposed is fairly limited but we can conceivably extend it in quite a few directions, e.g. storing first-class user-provided transaction metadata