Duplicate error messages: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 5: Line 5:
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.  
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. [[User:Ttenbergen|Ttenbergen]] 11:22, 2022 April 21 (CDT)
Implementing [[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)

Revision as of 10:58, 2024 April 24

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 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)