I am sorry to say this behavior is not a bug but is describe as follows in the UFT Object Model Reference > Utility Objects > Utility Statements > [RunAPITest](http://uft-help.saas.hpe.com/en/12.54/UFT_Help/Subsystems/OMRHelp/OMRHelp.htm#OV_Supp_Util/Utility_Utility_RunAction.htm) statement.
- The *RunAction* statement can run only actions that are already associated
with your test as part of the test flow. Therefore, in order to enter a
*RunAction* statement in the Editor for an external action, you must first
insert a call to the action (Design > Call to New Action) or copy the
external action (*Design > Call to Copy of Action*) into your test.
Using this option associates the action with the test and also inserts a
*RunAction* statement for you. After the external action is added to the
test flow, you can add additional calls to that external action in the
- If you insert a *RunAction* statement in the Editor for an external action
that is not already associated with your test as a part of the test flow,
the *RunAction* statement fails. For more details on copying or calling
external actions, see the *HP Unified Functional Testing User Guide*.
- Do not use this statement to call an external action from within a function
library. Instead, use the *LoadAndRunAction* Statement.
- This statement is not supported in the Console Pane (Debug panes).