Make the engine re-read the database verifiedcriticalWritten by the Hub
The engine does not notice database changes on its own; one broker message makes it re-read at once.
In detail
A write through the console or through the console's own API reloads automatically — the engine did it, so it knows. A write straight to the database does not, and the delay is not small: ten minutes of a node behaving as though the change had not been made. The reload is cluster-wide by design, since the exchange is a fanout: every node reading that broker re-reads its settings. On a single-node installation that is invisible; on a cluster it means a change to one node's rows is applied everywhere at the same moment, which is usually what we want and always worth knowing.