Office nodes, spooling and reconnection

Office node

An office node is a managed component at a remote location. It registers and provisions with DES, receives authorised configuration and sends heartbeats.

During an outage

When connectivity to the central system is interrupted, an authorised local component may retain outbound work or use central spool according to configuration. The goal is to avoid data loss and deliver after connectivity returns.

Monitoring

Watch last heartbeat, node state, pending spool and last successful synchronisation. A missing heartbeat does not prove mailbox-store failure; it may be a network, token or service problem.

Recovery

Restore the protected connection and verify node identity first. Then allow replay of accumulated records and monitor for duplicates or permanent failures. Do not manually delete spool data before reviewing trace information.