Dear Klaus,
As it is now, if there is serious trouble inside an action, apparently the action may abort. However, if there were any push'es and pop's inside the action, and it aborts between a push and a pop, then the whole stack becomes corrupt.
Such a problem is very hard to debug. I'm still in the process of figuring out which of my actions is aborting exactly where...
Therefore I have 2 requests:
(1) an onend="" event for <action>. It should always be executed after the action has ended, even if the action got aborted for whatever reason. Pop() statements can then be placed there.
(2) if an action aborts, it would be nice if one could see that as a warning in the trace log, if possible with the exact command that caused the abort.
Thanks for considering this.