MQTT functions break when ESP-MESH-LITE root node disconnects from router (AEGHB-732)

[Teesmo]

I have modified the mesh local control example to include mqtt capabilities, where I use them (mesh lite and mqtt) as communications media. I get sensor readings periodically using rs485, then send them to the cloud using mqtt at intervals. When I switch off the router, the root node (currently my only node) enters into a router scan, and underprioritizes my MQTT logic (I still get sensor readings at the set periods, only, the MQTT sending now happens sporadically, if ever). This disrupts my code's logic in that I lose a lot of sensor readings because the esp_mqtt_client_enqueue function is called undeterministically ( it is not at the time I expect it to, i.e, it ignores its 'trigger'). I would like to know

1. Does router scan supersede all other functions?
2. At what intervals is the scan done?
3. What can I do to mitigate this?