donk

Elmar, At our lab, I did exactly the same for the same reason. To me a very obvious improvement, extremely helpful to find from what part the error originated. I changed the colour of the Parse State Queue VI to distinguish it from the original. See the yellow coloured vi icon in the screenshot below. Now a wire "previous" state is available for error processing, which in my case is done in the white coloured subvi "ERROR". Would love to see this in the next update of the JKI SM :-) @Jim Kring I find it cumbersome to have multiple logins for multiple platforms. This is the JKI forum and you ask for feedback on GitHub? >> We've posted a related idea and request for feedback, here: https://github.com/JKISoftware/JKI-State-Machine/issues/11 >> [..] Should we, instead, make the Previous State available to all frames of the JKI State Machine (e.g. as an additional output to the Parse State Queue), [..] Yes, this is sufficient for me. Oh, and I should mention that I use the very helpful GPower error toolset (https://gpower.io/?lang=en) which allows for creating (and extracting)multiple errors on the "standard error wire". So then the JKI Error Handler frame can handle multiple errors, originating from a single frame.