Behavior of actions when staggering and reapplying

Content Authoring
1

I’m trying to better understand the behavior of enabling both stagger and reapply under execution behavior. We’re attempting to perform an action with the following behavior:

  • Runs between 4AM-6AM client local time
  • Reapply unlimited number of times, waiting 1 day between reapplications
  • Stagger over 90 minutes

Each target system is expected to become relevant again within 3 days. However, the problem is that the stagger function isn’t working as expected. Whenever the action reapplies, most devices begin right at the beginning of the constraint window (4AM) rather than the randomly distributed start delay (sometime between 4AM-5:30AM).

It seems like the stagger only applies to the first application and subsequent reapplications no longer delay the start time. Or perhaps I’m misunderstanding, but either way is there any recourse? I could probably find another way to stagger the action outside of the execution behavior if needed.

2

Did you use the " Start client downloads" option ? Take a look at the following KB arcticle: https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0100498

3

Yes I’m familiar with that option, but this action doesn’t require any downloads - it’s a reoccurring action we use to restart devices that have an uptime of 3 days or have “Pending Restart” flags. We’re attempting to stagger the action because our network admins claim one of their appliances is being overwhelmed with new sessions as thousands of devices reboot at the same time.

Unless I’m missing something with our execution behavior this may just be a bug and we’ll implement the stagger directly in the actionscript or PS if necessary.

4

Then it sound like a bug not sure it is related to the specific type of action. Please open a custom support case to get an help how to resolve your issue