Alteryx Server Discussions
Find answers, ask questions, and share expertise about Alteryx Server.
I'm a bit behind on writing this question. We upgraded from 21.4 to 23.2. (.89 patch 2) earlier in the year. Since the upgrade, I've noticed one small change with the MongoDB. Previously in 21.4, in the AS_Queue table in the MongoDB I could get the error field out of the service data blob (__ServiceData). Now in 23.2 the service data has been replaced by various fields that contain the same error for my prior runs. For all runs that have taken place on 23.2, the error field is never populated, even when a run encounters an error. Is anybody else experiencing this as well? If there is a different table where the errors messages are stored, let me know!
For example, here are 3 key fields from the AS_Queue table. That first row is an error from several years ago. The error field is populated. The bottom row is from today, and the workflow errored out (AlteryxResultCode=2) but the error wasn't captured by Mongo like I think it should be.
In 2023.2, you can check.'AS_Results=>OutputLog', I guess.
It stores data as binary so parse that field with the below '?' tool. (I copied & pasted it from Server Usage report macro)
