Related to this post, I am wondering if additional context can somehow be made visible for trigger error messages to identify the specific action/transition that is causing the error, rather than having to manually create message actions to locate the last successful trigger action…
Behind the scenes, are trigger action/transition elements addressed/identified and can this be exposed for debugging?