After problematic SAR profile message crashes the RAO optimizer pod, it doesn't get ACKED/moved to dead-letter queue, just re-queued back into same rao.violations queue. After pod restart same message gets handled, killing the pods and repeating the process. Only way to unstuck the optimizer is to manually ACK the message.