Duplicate error messages: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| 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. | ||
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. [[User:Ttenbergen|Ttenbergen]] 11:22, 2022 April 21 (CDT) | |||
This problem | This problem is worse when we use soft-checks, since those will remain for the duration of a record being on the laptop. Example: [[Query s tmp Boarding Loc ER delay reasonable]] [[User:Ttenbergen|Ttenbergen]] 11:10, 2024 May 1 (CDT) | ||
Latest revision as of 10:10, 2024 May 1
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)
This problem is worse when we use soft-checks, since those will remain for the duration of a record being on the laptop. Example: Query s tmp Boarding Loc ER delay reasonable Ttenbergen 11:10, 2024 May 1 (CDT)