Overall Advanced Multi-row queue sequence interrupted.

BatchPatch Forums Home Forums BatchPatch Support Forum Overall Advanced Multi-row queue sequence interrupted.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #8952
    ScottE
    Participant

    I am trying to run an advanced multi-row queue sequence with the first step set to the following:

    Check for available updates

    Terminate queue if previous ‘Check for available updates’ finds 0 updates

    Download and install updates + reboot always

    Wait for host to go offline and come back online

    Check for available updates

    Terminate queue if previous ‘Check for available updates’ finds 0 updates

    Download and install updates + reboot if required

    Wait 5 minutes

    Check for available updates

    Terminate queue if previous ‘Check for available updates’ finds 0 updates

    Download and install updates + reboot if required

    The second and third steps are set to email various groups.

    If I have “Terminate queue if previous ‘Check for available updates’ finds 0 updates” as part of the first step and that terminates the queue because it found 0 updates, the entire advanced sequence stops and steps 2 and 3 don’t occur. If I remove “Terminate queue if previous ‘Check for available updates’ finds 0 updates” from the first step, it works fine and completes steps 2 and 3.

    Is there any way to have this work without terminating the entire sequence? I really want these steps to run sequentially without any delay, so I don’t want to schedule the email steps separately. Thanks!

    Scott.

    #10441
    doug
    Moderator

    Scott – You found a bug. We’ll have this fixed for the next release.

    Thanks,

    Doug

    #10442
    ScottE
    Participant

    Thanks for looking into it!

    #10012
    laurnwerner
    Participant

    this ever get fixed? i am having the same issue. I am using version 2018.10.4.13.0

    #10016
    doug
    Moderator

    It was fixed last year in version 2017.11.09. Are you sure you are encountering the *same* issue as described in this posting? I just tested 2018.10.4.13.0 and it works properly, so I suspect if you are encountering an issue, it’s not the issue that is described in this posting. Please be as descriptive as possible when explaining the issue that you are encountering.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.