When a package deployment is initiated, the agent sends a Package Status to the Axeda Platform at every point in the process. A deployment may fail for several reasons. The Platform will retry software package deployments for the following reasons:
o if the agent shuts down in the middle of a deployment (and restarts at a later time) - if this is the case, the Platform determines is there are any interrupted deployments for the agent and attempts to retry those deployments.
o if the agent experiences network issues during a deployment - when this is the case, the Platform will review the error codes sent by the agent. The Platform supports retrying package deployments for any possible agent error code. When the Platform receives an error code for which it is defined to retry package deployments, it will attempt a retry of the related packages.
The possible agent error codes that may be defined to trigger a package deployment retry are as follows. (The actual error code(s) defined to trigger a deployment retry will be specific to your Platform configuration.)
# 0 : failed
# 1 : version
# 2 : bad-format
# 3 : unknown-soap-method
# 4 : unsupported-function
# 5 : dataitem-not-found
# 6 : registry-name-not-found
# 7 : registry-file-read-error
# 8 : invalid-dependency-expression
# 9 : no-files-found
# 10 : some-files-not-found
# 11 : download-execution-failure
# 12 : archive-error
# 13 : read-error
# 14 : http-status-error
# 15 : checksum-error
# 16 : connection-failure
# 17 : socks-failure
# 18 : http-failure
# 19 : ssl-failure
# 20 : agent-shutdown
# 21 : download-checksum-error
# 22 : partial-file-missing
# 23 : invalid-directory
# 24 : restart-of-gateway-device
# 25 : soap-function-error
# 27 : multifile-uncompressed