Severity field in workflow properties | Community
Skip to main content
dannycollins
dannycollins
Level 2
May 18, 2017
Solved

Severity field in workflow properties

  • May 18, 2017
  • 4 replies
  • 3586 views

Hello,

What is the functional purpose of the "Severity" field in workflow properties (I have v6.1)?

My understanding is that it only has descriptive purpose as described in the documentation. But I'd like to make sure that it won't have any negative impact on my workflows. Can someone confirm this or correct me?

Thank you,

Danny

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Adhiyan

    Hi Danny,

    Yes, this field is only for indicative purpose and does not affect the actual execution of the workflow.

    4 replies

    Adhiyan
    Adobe Employee
    AdhiyanAdobe EmployeeAccepted solution
    Adobe Employee
    May 18, 2017

    Hi Danny,

    Yes, this field is only for indicative purpose and does not affect the actual execution of the workflow.

      dannycollins
      dannycollinsAuthor
      Level 2
      May 18, 2017

      Thanks a lot!

      vraghav
      Adobe Employee
      vraghavAdobe Employee
      Adobe Employee
      May 19, 2017

      Hi Danny,

      The severity field has a purpose.

      When you create a workflow inside Campaigns, it becomes a Campaign workflow. Execution of it is then handled by a parent workflow called Campaign Jobs or operationMgt.

      This workflow identified how many concurrent processes it can run based on an option nms_LimitOCncurrency which is by default set to 10.

      So, if you have to say 25 processes to be executed, if you wish to have your workflow make the cut, you can set a higher severity so that it can be accommodated in the available pool of 10 concurrent processes.

      Regards,

      Vipul

        dannycollins
        dannycollinsAuthor
        Level 2
        May 22, 2017

        Thanks a lot Vipul for this complete answer!

        Danny

        Terms & ConditionsAccessibility statement

        Loading footer...