-
Notifications
You must be signed in to change notification settings - Fork 386
Improve logging of the submission validation process #764
Comments
Again Risk 6 key is missing in hour-file 2020-09-15-hour-22.zip |
@Tho-Mat, thanks for the pointer. |
@michael-burwig |
@michael-burwig |
Hello @Tho-Mat , Thank you for the additional information. We are investigating this further together with the mobile team. |
@EvgeniiSkrebtcov |
and again for 2020-09-21-hour-06.zip |
another for |
some new sets arrived at That looks to much. Maybe the assumption is not correct. |
What exactly is the planned proceeding / timeline for this ticket? As to my understanding, this is already (fully or only partly?) implemented and merged (PR #783), but I don't (don't yet?) see it mentioned in the release notes for the upcoming release 1.4. What is the prio to analyse / understand the root cause of the missing keys? |
Hello @ndegendogo, |
The enhancement suggested by @Tho-Mat, and based on the discussion in #723
Current Implementation
Issue #723, demonstrated that currently implemented logging is not sufficient for effective troubleshooting of the submission validation process.
Suggested Enhancement
If the kay can not be saved in a DB (e.g. because it is already in database / Date to high / Date to low / unknown), we log this fact, date of the issue and the reason in the application logs.
Expected Benefits
This would have the great advantage of better analyzing certain constellations that can lead to errors.
The text was updated successfully, but these errors were encountered: