rakshay (Customer) asked a question.

July 13, 2025 at 12:40 PM
is it still possible to skip a node in a Workflow node? specifically delay nodes

In recent Workflow versions, it is no longer possible to use the "skip node" functionality, which we sometimes use to skip a delay node, during testing.

Is there a workaround or some other way to accomplish this?

  • 6 answers
  • 167 views

  • Boris.Lekumovich (RSA)

    Try changing the state of the node, selecting Skip and click on Change State

     

    image

  • rakshay (Customer)

    Thanks Boris,

    I tried on 8P7HF1 :

    • The WF was marked complete
    • It seems none of the nodes following the one I set to "skip" were executed.

     

    see the screenshot - note circled in red - the line is not green

    Also, if I use "show active path only" I see all the nodes up to the Delay node, and nothing past.

     

    Do you have any idea?

     

    image

    Expand Post

  • OverthinkerDave (Customer)

    I have also noticed this strange change in 8.0

    For delay nodes it seems you need to use "cancel" in 8.0, and "skip" in pre 8.0 versions 😂

     

    Who made these design decisions, I do not know 😭

  • rakshay (Customer)

    Confirmed!

    Using Cancel practically skipped the node, and using Skip canceled the rest of the WF...

     

    Many thanks @OverthinkerDave (Customer)​  I appreciate your help!

     

  • OverthinkerDave (Customer)

    I have a new update to this node state confusion (which was introduced in 8.0.0).

    (and if you open up this entire post I have a suggestion of improvement I would like all to give feedback on)

     

    In earlier versions (like 7.5.0) the change state had different labels.

    • "Cancel" option (in 8.0.0) was called "Complete Node" (in 7.5.0)
      • and according to admin manual in 8.0.0 (around page 258) means "Complete node/activity"
    • "Skip" in all versions of this product has always meant "cancel"
      • or more precisely "cancel current workflow"
    • "Suspend" is legacy, and I think that option is going to be removed soon

     

    The above is confusing.

     

    So I have a improvement suggestion:

     

    • Re-instate the label "Complete Node", and let it "skip/complete" a (any) node in a workflow. And NEVER show the option cancel.
    • Rename the label "Skip" to "Cancel Workflow" or "Cancel Job". Because this is what this old "Skip" option ALWAYS have done.

     

    Please give feedback on this.

    I could make a survey monkey feedback, to make an idea for enhancement.

    But it is always good to hear from others what they think.

     

    Also if giving feedback here:

    • Help me out what I should write under the "3rd option" in the survey monkey form :
      • "Please describe the potential benefit or value this would provide you or your organization."

     

    Expand Post

  • rakshay (Customer)

    All in all this sounds good to me, I would expect the UI to do 2 things:

    1. describe my available options
    2. explain the possible impact of my decision. so, if I hit a button called Complete Node does this implies the WF would resume with any following actions?, and if I could, I'd probably want a "cancel job\WF" or perhaps "Abort WF"

     

    as for potential benefit or value, my 2 cents:

    "Increase operators' confidence when handling incidents such as a stuck WF or request.

    Resolve a confusing button name change introduced in Version 8 to minimize the risk of operator error due to misunderstanding. "

    Expand Post

Don't see what you're looking for?