This is an expected behavior. It occurs after site creation or site update if:
- One tunnel is up while the second one is in an undefined state, i.e., it is not yet connected.
- An additional ISP/identifier was added from the SDWAN side configuration on the portal but this new connection was not yet configured to establish a VPN tunnel.
In both scenarios, since it is not clear why the new connection is not configured, a blank warning without any events appears.