When a job is run on a device, the file(s) associated with the job are stored on the local device.
If later the same job is scheduled on another device which is on the same subnet, the device may download the file for the job from the device that already has the component file. This will speed up the component deployment and reduce the load across the internet connection.
Before a job is run, the device sends out a network broadcast looking for the file. If the file is found, it will be downloaded from the Connection Broker.
Note: A Local cache always has higher priority than an agent located on the device. This is due to the fact that a local cache synchronises all files periodically while a regular agent does not.