# Exception transitions Exception transitions visually differ from normal transitions. They are represented by a dashed line instead of a solid line and are also displayed in a different color. Typically, when a sequence throws an error, it stops execution. However, if an exception transition connects it to another sequence, the operation will continue and proceed to the linked transition.

In this example, if Sequence 1 throws an error, the robot will proceed to the Sequence 3 instead of Sequence 2.

Like normal transitions, exception transitions also allow conditions to be specified within them. A sequence can contain multiple exception transitions for precise control over the workflow:

In this example, if either Click Control or Rename Sheet throws an error, we can create a transition for either of them.

### Useful conditions: LastError.ActionMessage -> Contains the message of the last error. LastError.ActionOutcome -> Contains the message showing the outcome of the action: ***True/False*** LastError.Matches("") -> Can be used to check if an error matches a given string. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tailent.com/getting-started/tap-studio/transitions/exception-transitions.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.