We are seeing an issue where any time the platform MQ connect pod is kicked/redeployed/promoted, we experience WAL growth despite the heartbeat settings in our Debezium connector

Its possible moving to using a table for heartbeats vs the logical emit message is a fix but thats unconfirmed yet by debezium team (long thread here)

The fix is to make a few API requests to trigger debezium at least once and then it goes away and heartbeats seem to work again. We need to determine the root cause of the issue, and in the interim find a solution that prevents the issue and reduce alerting noise.