Quote:
Originally Posted by applegaa
You can create a custom column for those errors if you want to retain them.
On the "Custom Columns" tab, there is a section at the bottom labeled "Special column:" and you want to create a column and add it to "Update/Overwrite Error Column:". I don't check the "Save All Errors" box, so I only see error messages if the last run failed. Granted, stories with no updates are listed as bad but have no error message, so you will only see them if you use the "View Log" button others have mentioned.
I wish that it had Good/Bad/No instead of just Good/Bad, but the current system works.
- Andrew
|
I actually do a bit of cheating. I have two columns for the errors. The first is for the error being reported (error_messages) and have that hidden in the tag browser. The second is a column built from that first one that behaves like tags (errors). then I use a programming template that takes the first few characters of the error message in the original column and have it identify its own error message for it.
the error about the bad update because there hasn't been an update translates to website current. Different sites seem to result in different messages, so multiple errors report the same. makes things a lot easier when I only have to look at a half dozen different errors
the 525 error occasionally thrown by A03 the last couple of months, I have it translate to "Too many requests", then I can go back later and select just the stories that threw that error and try to update them again.
want to see what has not thrown an error? just I click on errors twice so it gives a 'search' of #errors:false and get a list of what has thrown no errors since the last time a story was updated
It may not be the most elegant solution out there, but it works and that's what I care about