By its very nature, "Try Next Alternative" error handling refers to a Try step. This Try step must be a prior step on the current execution path, that is, it must be one of the steps whose execution led up to the current step. Otherwise the "next alternative" part of "Try Next Alternative" does not make much sense.
This opens an interesting possibility: What if there are several Try steps on the current execution path? If that is the case, the robot will be in the process of executing a "current branch" relative to each of these Try steps, and for each of them the "next branch" will be a different one. For example, if an error occurs in step B in the following robot, "Try Next Alternative" will continue execution at
the next branch at the rightmost Try step, so that execution skips step C and continues at step D; or
the next branch at the leftmost Try step, causing execution to skip both steps C and D and continues at step E?
The answer is that you can choose which one, as seen in the error handling configuration for step B:
The default is the "nearest Try step" but other Try steps on the execution path can be selected explicitly. The reference to the Try step is by name; if several Try steps have the same name, the nearest (rightmost) one with that name is implied. This can be used to advantage as described in Try-Catch.
Although we here describe "At" targets only in relation to "Try Next Alternative" error handling, such references may be used also with the "Next Iteration" and "Break Loop" error handling options that are described in the following section. In those cases, the references will be to loop steps rather than Try steps.