Get from Queue
- 01 Jun 2023
- 2 Minutes to read
- Contributors
- Print
- DarkLight
- PDF
Get from Queue
- Updated on 01 Jun 2023
- 2 Minutes to read
- Contributors
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
The Get from Queue node enables you to retrieve tasks from any Queue node that you have set up in your Сorezoid processes (see Picture 1).
Picture 1. Get from Queue node task flow when used with the Queue node
Node Settings
Basic settings
Process with the Queue Node - the process in which the Queue node is located.
Queue Node - the Queue node from the above process.
Take From The Queue Start/ Take From The Queue End - allows you to specify in what order to get tasks.
Other
Alert if the number of tasks in the node queue reaches the following number - If this option is selected, a new condition will be created within the node. It will allow you to monitor whether the number of tasks in the node exceeds the specified threshold.
Maximum interval, for which the task stays in the node before being forwarded - the amount of time a task is allowed to be in this node. Can be specified in seconds, minutes, hours, or days. It can also be specified as a unixtime function. This value must be at least 30 seconds.
Examples
When a task enters the "Get from Queue" node, it triggers the node to retrieve the next task from the configured Queue. The retrieved task's values are then added to the current task and can be accessed under the "queue_task_data" parameter. Additionally, the ID of the retrieved task can be found in the "queue_task_id" parameter (see Picture 2).
Picture 2. Using the Get from Queue node to retrieve a task stored in the Queue node and add parameters to it
Error handling & troubleshooting
When an error occurs in the node, a task goes to the auxiliary Condition output node:
Picture 3. Get from Queue node's auxiliary output node
This auxiliary Condition node is used for storing error parameters. With that, the following fields are added to the initial task depending on the error and node type:
| Error parameter name | Parameter description |
|---|---|
__conveyor_node_type_return_type_error__ | Error type: hardware (system error), software (error in a node logic/settings) |
__conveyor_node_type_return_type_tag__ | Error tag (see the *-marked errors in Error tag column of the table below) |
__conveyor_node_type_return_type_description__ | Error description in human-readable language. Can be static or dynamic |
| Problem/Error tag | Cause | Solution |
|---|---|---|
| *"not_found_task" error | The Queue node is empty | Make sure to account for this case when designing your process. You can do this by setting up the "Alert if the number of tasks in the node queue reaches the following number" option. |
| *"access_denied" error | You do not have access to the process that contains the Queue node you are trying to access. | Make sure you specified the Queue node correctly. If that is not the issue, request access to the Queue node process. |
| *"No queue logic in conv_id: {{ConvId}} node_id: {{NodeId}}" error | The process you specified does not contain a Queue node. | Make sure you specified the process correctly. |
| *"conveyor_is_not_active" error | The target process is not active | Please ensure that the Queue process is active. |
| *"get_task_wrong_convert_param" error | Parameter value failed to convert | Please check and correct the data type of the parameter mentioned in the error message. |
| *"crash_api" error | Error of retrieving the task | Please consult with your administrator for further assistance. |
| *"Error running get task" error | Task copy error | Please verify if the task ID specified is valid (task with this ID exists). If it is valid, please consult with your administrator for further assistance. |
*the node errors that are listed with the exact error tag (conveyor_node name_return_type_tag).