...and this is bad. Waiverdb consumer checks for each policy related if
there is a decision change and if it has to publish a message about it.
But if an error occurs during the decision (real life example: the
policy with the specified parameters does not exist) the consumer just
raises an exception and does not continue with the other policies.
...and this is bad. Waiverdb consumer checks for each policy related if
there is a decision change and if it has to publish a message about it.
But if an error occurs during the decision (real life example: the
policy with the specified parameters does not exist) the consumer just
raises an exception and does not continue with the other policies.