As a developer, I want to investigate and address the tasker-broker communication issues reported in VLab #132157

[HankHerr-NOAA]

In the 7/11 dev all, I asked,

The tasker’s connection to the broker appears to breakdown during the weekend backups. Should we add code to the tasker to reset those connections when that happens?

Notes from that conversation:

Unsure. Will need some investigating. Do we establish a channel once and then connect through it repeatedly, or connect the channel every time? Unsure. We can probably add some more resiliency. I brought up the Up/Down check. Can we use that to detect the problem and trigger a health check to force a cycling? Again, needs investigation. Could be the broker that would need cycling, not the tasker.

This ticket is for the investigation and potential enhancement to address the miscommunication by (probably) cycling the service, unless just the broker would fix it. See the VLab ticket for information recorded during the event.

Hank