Save in db with hierarchy-based alert suppression

We have alerts that use the hierarchy-based alert suppression system, but we have encountered a problem:

When the father alert is triggered it inhibits the daughters, that is correct, the triggers are not activated, but the alert continues to be saved in the database and that causes a dissonance of data between the monitoring based on the database and the alert system.

Is there any solution like also inhibiting saving in the database?
Or should we outsource to a script through the topic in which the alert will be saved?

Regards, and thank you very much!