Duplicate error messages: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
Line 3: Line 3:
These are based on the events used to trigger error messages.  
These are based on the events used to trigger error messages.  


* I think I have eliminated most of them - '''collectors, please log here any that I may have missed'''. Ttenbergen 18:29, 2012 November 7 (EST)
The reason it shows up repeatedly recently is that we are implementing more "soft" checks. They use the same triggers as "hard" errors, and we would want to make sure we catch those, and they wouldn’t show up repeated because they would likely be fixed after they first show up.
** no answers, assuming fixed Ttenbergen 11:49, 2014 September 10 (CDT)


One example dealt with in a different article is [[Multiple LOS errors]]. Ttenbergen 11:30, 2013 October 9 (CDT)
Implementing [[User:Ttenbergen/Cross Check Engine]] would take care of this but it's a major change I haven't had time for. [[User:Ttenbergen|Ttenbergen]] 11:22, 2022 April 21 (CDT)
 
This problem showed up again now that we are using more "soft" checks. Implementing [[User:Ttenbergen/Cross Check Engine]] would take care of this but it's a major change I haven't had time for.

Latest revision as of 11:22, 2022 April 21

Some error messages in CCMDB.accdb created by CCMDB Data Integrity Checks create more than one error message. These are based on the events used to trigger error messages.

The reason it shows up repeatedly recently is that we are implementing more "soft" checks. They use the same triggers as "hard" errors, and we would want to make sure we catch those, and they wouldn’t show up repeated because they would likely be fixed after they first show up.

Implementing User:Ttenbergen/Cross Check Engine would take care of this but it's a major change I haven't had time for. Ttenbergen 11:22, 2022 April 21 (CDT)