A Remote Broker object also maintains a queue, called the forward queue. The forward queue contains instances of documents that match subscriptions in the Remote Broker object's subscription list. When the remote Broker is connected to its Remote Broker object, it continually retrieves documents from this forward queue and distributes the documents to its own clients.

A Remote Broker object is similar to an explicit-destroy client-state object in that it remains instantiated even if the remote Broker disconnects or goes offline. When the remote Broker comes back online, it automatically reconnects to its peers and retrieves documents from its forward queues.

Certain conditions can cause a Remote Broker object to become orphaned, meaning that the Remote Broker object exists for a Broker that has been permanently deleted or removed from the territory. An orphaned Remote Broker object will continue to collect documents in its forward queue and can potentially consume a great deal of storage if it is not administratively removed. To delete an orphaned Remote Broker object, see Deleting a Remote Broker Object.