In the context of this topic, keep in mind that the Axeda® Agents treat all file uploads as SM packages, no matter where the request originates. References to "packages" in this topic always reference both SM packages and file upload requests.
File upload requests can originate through File Upload actions, rules configured with File Upload actions, Upload requests from the Axeda® Service application, and Software Management (SM) packages. Uploads can also originate from the Axeda Agents, when logic schemas and File Watchers are configured in the Agent project. File upload requests originating from the Axeda Platform always have a medium priority. File uploads originating from the Axeda Agents always have a low priority.
Axeda Gateway and Axeda Connector support concurrent execution of packages. You can configure a maximum number of concurrently executing packages when configuring the project using Axeda Builder. If a new package is deployed while another package is being executed by the Agent, the Agent will either execute the new package (as long as the maximum number of concurrently executing packages is not exceeded) or place the package in its queue. Either way, the Agent does NOT preempt currently executing packages. To avoid the situation where execution of one package delays the execution of other packages, Axeda recommends that you set the maximum number of concurrently executing packages in the project to a number appropriate to your expected needs. For example, the default maximum number is 64. If you expect that 70 packages (remember to include file upload requests) may be sent to the Agent either at the same time or very closely together, then change this maximum number to 70.