The all polling jobs for VMware systems are rescheduled when the "SolarWinds Orion Module Engine" service is (re)started on main poller. There is one known issue with rescheduling nodes on additional pollers. If "SolarWinds Orion Module Engine" service can't connect to job scheduler on additional poller (poller is down or services are stopped) then the rescheduling failed for nodes on this additional poller. Then your approach with disabling/re-enabling polling is necessary.
This situation can also happen for nodes on main poller if "SolarWinds Job Scheduler" services is stopped when "SolarWinds Orion Module Engine" service starts, but Configuration Wizard or Orion Service Manager application start the Scheduler service before Module Engine service. So this situation shouldn't happen if the "SolarWinds Job Scheduler" service isn't stopped manually.
Could you confirm one of these situations?
Lukas Belza (SolarWinds development)
We are using an additional poller and that is where those systems are polled from.
Is the disabling/re-enabling the polling the only workaround at this time?
Are there plans to resolve this problem in the future?
I would like to get follow-up response on this. This particular issue has caused us a lot of problems.