Throw Error Node

Created by Rico Stodt, Modified on Mon, 31 Jan, 2022 at 11:47 AM by Rico Stodt

This page provides a detailed overview about the Throw Error Node.


Contents


Node Description


ThrowError 5 1.png


Throw Error Node


Intera will automatically throw a variety of low-level errors that it detects, such as errors associated with the physical state of the robot or devices, or errors encountered during moves. The Throw Error node is available to throw user-specified errors, such as if a mispick occurs. The error will only occur if the node becomes active. This type of error must be specifically defined by the user in the behavior tree. The Throw Error node is useful when it is possible for a task to get into a state in which user intervention is required for the task to proceed.

The Throw Error node is often used in conjunction with the Catch Error & Error Handler nodes. More information about the implementation of this node can be seen in the Error Handling tutorial.


Node Type


Primitive - Cannot have children.


Node Editor


Throw Error Node Inspector.png


  • ID

Not editable

  • Name

Auto generated and user editable

  • Error Id

This is a string that uniquely identifies the error. It will appear under the Behavior Tree card within a selected Error Handler node.

  • Comments

User editable - add comments about this node.


NOTE


Throwing an error will immediately stop the task. The task can be continued from its stopping point. Users are advised to properly manage any signals or variables which control the execution of the Throw Error node. In order to keep the task running, use Catch Error & Error Handler nodes. When an error is thrown, workspace snapshot can also be taken and saved to the task's snapshot gallery or sent to a configured email address.

 

 


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article