Contents x
Get from Queue
  • 31 Oct 2024
  • 2 Minutes to read
  • Contributors
  • Print
  • Dark
    Light
  • PDF
Contents

Get from Queue

  • Updated on 31 Oct 2024
  • 2 Minutes to read
  • Contributors
  • Print
  • Dark
    Light
  • PDF
Article summary

Overview

The Get from Queue node enables you to retrieve tasks from any Queue node that you have set up in your Сorezoid processes.
Get from Queue flow

Settings

The Get from Queue node has the following parameters:

  1. (Optional) Title and Description: Name and details of the node.

  2. Basic settings:

    • Process with the Queue Node: The Process where the Queue node is.
    • Queue Node: The Queue node from the Process above.
    • Take From The Queue Start/Take From The Queue Start: Specifies in what order to get tasks.

  3. Other:

    • Alert if the number of tasks in the node queue reaches the following number: Helps monitor whether the number of tasks in the node exceeds the specified threshold. When selecting the checkbox, you have to enter the needed number of tasks in the field that appears below.
    • Maximum interval, for which the task stays in the node before being forwarded: The amount of time a task is allowed to be in the node can be set in seconds, minutes, hours, and days.
      Note: The checkbox has a minimum value of 30 seconds. You can set a shorter interval by using the Unixtime function.

    Get from Queue settings

Examples

Using the Get from Queue node to retrieve a task stored in the Queue node
See the example in Queue.

Error handling & troubleshooting

When an error occurs in the Get from Queue node, a task goes to the auxiliary Condition output node that is used for storing error parameters.

image.png

When an error occurs during the task processing, you may see the following error parameter names in the task.

Error parameter nameError type
__conveyor_get_task_return_type_error__Hardware (system error), Software (error in a node logic/settings).
__conveyor_get_task_return_type_tag__*Error tag.
__conveyor_get_task_return_type_description__Error description in human-readable language; can be static or dynamic.

*The error tag __conveyor_get_task_return_type_tag__ may have the following values.

ValueCauseSolution
access_deniedYou don't have access to the Process you are trying to call.Contact the Process owner to get access.
access_deniedYou are trying to send or receive tasks from another stage.It's not allowed to get and send tasks between stages. Use the same stage to send and receive tasks.
No queue logic in conv_id: {{ConvId}} node_id: {{NodeId}}The Process you specified does not contain the Queue node.Make sure you’ve specified the Process correctly.
conveyor_is_not_activeThe target Process is not active.Make sure that the Queue node Process is active.
get_task_wrong_convert_paramParameter value failed to convert.Check and correct the data type of the parameter mentioned in the error message.
crash_apiTask retrieval error.Contact your administrator for further assistance.
Error running get tasTask copy error.Check whether the specified task ID is valid (a task with this ID exists) or contact your administrator for further assistance.
not_found_conv_by_aliasYour alias is linked to a Process that no longer exists.Use an existing Process.
get_task_size_overflow_limitThe size of the task data exceeds the specified limit set for your environment.Reduce the size of your task.
bad_callback_nodeThe Process you are calling doesn't have the Callback node.Create the Callback node in the Process you are calling.
get_task_executing_errorThere is an unexpected error.Contact the support team for further assistance.
not_found_taskThe Queue node is empty.Make sure to consider this case when designing the Process by selecting the Alert when the number of tasks in the node queue reaches the next number option.
Was this article helpful?
What's Next