The thought, originally, is that getting the same exception for multiple events could flag a database connectivity event.
However, this is also likely the cause from some content / bug combination. Thus, this proposed to revert that logic.
Counter-argument which then comes up is how to handle resiliency needs.
https://github.com/ansible/awx/compare/devel...AlanCoding:awx:raise_revert?expand=1