If an error occurs during the name historization, there are no information about it except in the log
|Assignee:||Nicolas CHARLES||% Done:|
|Category:||Web - Maintenance|
|Pull Request:||How to reproduce:|
|Reproduced:||Found in version(s):|
I seem to recall it was a deliberate choice to accept that it could fail and not prevent normal execution. However, except by looking at the logs, there are no way to know that something went bad.
Maybe some monitoring in the log could warn the administrator ??
#4 Updated by Nicolas CHARLES over 3 years ago
When we change names of groups, directives, rules, or their content, they are historised in the SQL databases for tracability during deployment of promises
However, if for some reason their historization fails, there is nothing except in the logs that will warn that the historization failed.
It's better that it's not blocking (why would we prevent deployment because a name cannot be stored in database), but a bit of information would help
Probably the new sysadmin logger would be useful in this case