Priority Modify

modify runner priority

Overview

This node modifies the priority value of incoming runner items. It is useful in scenarios where you want to dynamically adjust the execution priority of tasks or jobs within a workflow, such as increasing priority for urgent tasks, decreasing it for less important ones, or setting a specific priority level directly.

For example, if you have multiple tasks queued and want to boost the priority of certain tasks based on external conditions, this node can increase their priority values accordingly before passing them along.

Properties

Name Meaning
Mode Defines how to modify the priority: "Increase" adds the specified number, "Decrease" subtracts it, and "Set" assigns the exact priority value.
Priority The numeric value used to increase, decrease, or set the priority depending on the selected mode.

Output

The output contains runner items with their priority values modified according to the selected mode and priority number. Each item’s priority is recalculated and wrapped in a new runner object reflecting the updated priority.

No binary data is output by this node.

Dependencies

  • This node requires input runner items from a previous node.
  • No external API keys or services are needed.
  • It depends on internal runner and connection types to handle priority modification logic.

Troubleshooting

  • Issue: Priority values not changing as expected.

    • Cause: Incorrect mode selection or zero priority value.
    • Solution: Verify that the "Mode" property is correctly set and the "Priority" number is non-zero when using increase or decrease modes.

  • Issue: Node receives no input runner items.

    • Cause: Upstream node did not output any runner items.
    • Solution: Ensure the previous node outputs runner items compatible with this node.

  • Error: Unexpected input type.

    • Cause: Input data is not of the expected runner type.
    • Solution: Confirm that the input connection provides runner-type data.

Links and References

Discussion