> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.eshepherd.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Prolonged Communication Outage

In some cases, communication between the virtual fencing neckbands and the cloud platform can be interrupted for an extended period. This can happen due to **cellular network outages**, **LoRa Base Station failures**, or other connectivity issues in the local area.

When communication is lost, the neckbands will **continue to enforce the existing virtual fence** until the configured **Emergency Timeout** expires (default: 24 hours).
During this time, the neckbands operate autonomously but **cannot receive new instructions** from the platform.



##### What Happens During an Outage

The neckbands maintain the **current virtual paddock boundaries** and continue normal operation.

As communication is unavailable, it is **not possible to**:
* Send new virtual fence boundaries.
* Turn off or modify the existing fence.
* Receive updated status or location data from the animals.

Repeatedly trying to send new instructions during this period will **create a backlog (“queue”)** on the platform. Once communication is restored, this backlog can cause **delays** as all the queued instructions are processed. It’s best to **avoid sending repeated updates** until connectivity is confirmed to be restored.


### Recommended Actions for Farmers

###### 1 - Assess Feed Availability

Determine whether the animals have **sufficient feed within their current virtual paddock** to last until the Emergency Timeout expires.
If feed is limited or the paddock is becoming overgrazed:
* Provide **supplementary feed**, such as hay or silage, within the existing virtual paddock.
* Avoid attempting to move animals virtually until communication returns.


###### 2 - Check Infrastructure

Inspect or confirm the status of any equipment that could be contributing to the outage:
* Verify that the **LoRa Base Station** has power and is operating normally.
* Check that **network coverage** is available in the area (for example, via a mobile phone on the same carrier).
* Ensure there are **no local power outages** or equipment faults.
If the issue appears local, restoring power or resetting equipment may resolve communication sooner.


###### 3 - Monitor Animal Behaviour

Even without live data, you can still observe the herd in person to ensure:
* Animals remain calm and are respecting the current virtual fence.
* None have breached the boundary or appear stressed due to limited feed or water.


###### 4 - Prepare Temporary Containment (if needed)

If communication cannot be restored quickly and the Emergency Timeout is likely to expire soon:
* Set up **temporary electric fencing** to maintain containment once the neckbands stop enforcing boundaries.
* Consider **moving animals manually** to a secure paddock if containment risk is high.


###### 5 - Wait for Communications to Restore

Once connectivity is restored:
* The platform will automatically **resume communication** with all neckbands.
* Virtual fences will **reapply** as per their last active configuration.
* Avoid making immediate large-scale boundary changes until all devices have confirmed reconnection.


###### Preventative Tips

To minimize disruption from future outages:
* Ensure **Base Stations** are installed in locations with reliable power and cellular signal.
* Set the **Emergency Timeout** to a duration that suits your farm’s risk profile and operational flexibility.
* Keep a small amount of **temporary fencing equipment** on hand as a contingency.



During a prolonged communication outage, neckbands continue to enforce the last known virtual paddock until the Emergency Timeout expires. Farmers should **assess feed levels**, **avoid sending repeated commands**, and **prepare contingency measures** like temporary fencing or supplementary feeding if needed.

Once communication resumes, normal operation will automatically continue.


v1.0, 11/2025