Deployments with heartbeat schedule


1 comment

  • Colby Bouma

    If Inventory scans the targets after the deployment and they leave the Collection, Deploy will not deploy to them again. Deploy always grabs the current members of the Collection when the deployment starts, not when the Schedule was created.

    When using Collections as Targets, I recommend disabling "Stop deploying to targets once they succeed" on the Options tab of the Schedule in case you need to deploy to them again in the future (such as when an update comes out).

    Also, keep in mind that the Heartbeat Trigger only fires when the target's Online status in Inventory goes from No to Yes.

    Comment actions Permalink

Please sign in to leave a comment.