Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Why do I get this error: ExitPoint executed but EntryPointArgs does not exist in InnerArg tree?

Updated on January 27, 2017

This exception indicates an automation that has both an entry point and an exit point and also has an event that bypasses the entry point and connects to an exit point:

ExitPoint executed but EntryPointArgs does not exist in InnerArg tree

To avoid this exception, always be sure to call the entry point from another automation.

Here is an example of the message you would receive:

Message example

This is incorrect:

Connection block example

This is correct:

Connectoin block example

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us