I'm seeing a significant number of ACN COMM events generated on a regular basis. The number of events routinely exceeds 35,000 per month. The vast majority of the events, 70%+, are all associated with the batch executive node losing communication on the primary ACN network. Reviewing the data I can see most of the events occur during monthly patching, which to some degree is expected as the server gets rebooted. Looking closer at time stamps there is a period of ~24-36 hours after the last server reboot that these events continue to be generated. Looking into this even further the problem did not exist prior to implementing a redundant batch server. My impact partner opened a GSC ticket for this issue in mid-March, and all GSC recommendations to this point have not improved or resolved this problem. I am curious if this is expected behavior with a redundant batch configuration? I do not get the impression GSC will solve this issue and I don't want to continue wasting time if this is typical with redundant batch systems. That said if it is not typical I want to continue pressing GSC for a solution.