Log Reader

I'm trying to read the contents of "design_errors.csv" (which appears to be a normally-formatted CSV file).  I've tried readCSVLog(), readCSVLogPaging(), and readCSVLogPagingWithHeaders(); all of them fail to pull back any contents.  They do receive the header column names from the CSV file, but return no rows of data.  Any suggestions?

Is anyone monitoring comments here?  April Schuppel perhaps?  I have a use case that requires me to be able to query this log file into the Appian UI, and no other workable ways have really been presented to us.

phorning - I had Appian Support deprecate the existing design_errors.csv files across all my environments, such that a new file has been created as of a few days ago, so that there is now a consistent number of columns across all rows.  Per my expectation, the log reader query now works fine.

Sam Zacks - for further clarification: I've had Appian Support deprecate the existing design_errors.csv in all my environments so that they can start over with consistent columns in all rows, and the log reader query now works fine, as I'd expected.

Sam Zacks - also, I wasn't notified of your reply until just now when someone clicked "like" on my top comment.  I suggest when replying to these you directly tag people and/or click "like" on the comment you're replying to.  It seems to me that Community settings should be refined such that people are notified of replies here.

Sam Zacks - your design_errors.csv file would (i presume) need to have some rows in it with the older version of the column set.  What do you see when you look?

Hi Mike, I am trying to reproduce what you have described on a 20.3.90.0 environment and it is not occurring. Are you still on 20.2 and are you still experiencing this issue?

Mike- based on your initial post and your reply below you'd thought that "around the upgrade to 20.2" the design_errors.csv log reader feed broke. But maybe it was a simple fix to include the new columns?

I'm not having any 20.2 issue, so I'm not clear what you mean or what the relevance is to this particular issue thread?  You might be referring to the one paulc noted in the prior top-level thread, in which case it might be most helpful to reply there and weigh in.

Hi Mike Schmitt and Somnath Dey any update on the 20.2 issue?

 Hi Mike Schmitt - I've reached out to the author to see if they can assist with the issue.

After some additional troubleshooting, my theory is that the CSV Log Reader fails due to the fact that around the upgrade to 20.2, the design_errors log picked up several extra columns (and because this was just appended to the same log file, instead of the existing file being archived and a new one begun).

After some additional troubleshooting, my theory is that the CSV Log Reader fails due to the fact that around the upgrade to 20.2, the design_errors log picked up several extra columns (and because this was just appended to the same log file, instead of the existing file being archived and a new one begun).

phorning - I had Appian Support deprecate the existing design_errors.csv files across all my environments, such that a new file has been created as of a few days ago, so that there is now a consistent number of columns across all rows.  Per my expectation, the log reader query now works fine.

Mike- based on your initial post and your reply below you'd thought that "around the upgrade to 20.2" the design_errors.csv log reader feed broke. But maybe it was a simple fix to include the new columns?

I'm not having any 20.2 issue, so I'm not clear what you mean or what the relevance is to this particular issue thread?  You might be referring to the one paulc noted in the prior top-level thread, in which case it might be most helpful to reply there and weigh in.

Hi Mike Schmitt and Somnath Dey any update on the 20.2 issue?

 Hi Mike Schmitt - I've reached out to the author to see if they can assist with the issue.