Delivery target becomes stuck in Sending Instructions (SCM Download)
This issue could be due to one of the following situations:
• The agent is not pinging or just has not pinged yet, and therefore has not received the package.
• The agent received the package, but either restarted or lost network connectivity before being able to send its updated status.
• The Thing representing the agent was deleted.
• The Message Store Subsystem was restarted.
• The ThingWorx Platform was restarted.
In the first two situations, you may need to wait for the agent to be able to communicate with the platform.
If the Thing was deleted accidentally, recreating it should allow the delivery target to continue. Otherwise, it may need to be allowed to time out, or may need to be deleted.
If the Message Store Subsystem or the platform are restarted, the delivery target should be able to complete successfully after timing out and retrying.
 |
The Sending Instructions timeout is one day (86,400 seconds) by default. It may be beneficial to lower or raise this setting (under > in the SCM menu), depending on the circumstance. If you expect some agents not to ping the platform within a day of the deployment being created, the Sending Instructions timeout should be raised to prevent delivery targets for those agents to time out in the Sending Instructions state. Alternatively, if delivery targets are stuck in the Sending Instructions state and appear to be pinging regularly, it is likely that the service invocations that tell the agents about the deployment have been lost, and therefore temporarily lowering the Sending Instructions timeout is a quick way to force those delivery targets to retry.
|