You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error 538401 is a general catch-all error for any errors that come up in the async writer that aren't locally handled (Background Wrier.vi under "report error" case). The async writer will send a message to the output.vi function which will result in a Critical error when the error coming out of Output.vi goes into the classify errors step.
The issue is that even though the async writer process tells the Output process what error it encountered, this information isn't then fed into the error classification step so users will see that an unhandled error occurred but not what that error is.
In Output.vi under the "False" -> "Exit" cases, we should simply forward the error under as an appended error string so when the critical error is logged, the user will be able to tell what error came up.
The text was updated successfully, but these errors were encountered:
Error 538401 is a general catch-all error for any errors that come up in the async writer that aren't locally handled (Background Wrier.vi under "report error" case). The async writer will send a message to the output.vi function which will result in a Critical error when the error coming out of Output.vi goes into the classify errors step.
The issue is that even though the async writer process tells the Output process what error it encountered, this information isn't then fed into the error classification step so users will see that an unhandled error occurred but not what that error is.
In Output.vi under the "False" -> "Exit" cases, we should simply forward the error under as an appended error string so when the critical error is logged, the user will be able to tell what error came up.
The text was updated successfully, but these errors were encountered: