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 does it take five seconds to move between regions or fields in automations which use a Text adapter?

Updated on February 13, 2017

When the text for a screen region is set in an automation, Studio's Text adapter pauses for a predefined period between each automation step. The period that the automation pauses is defined by the RefreshTimeout property.

The RefreshTimeout property is expressed in milliseconds for each Text adapter automation component and equals the number of seconds the automation pauses before checking for the screen text change event notification. The default is 5000 milliseconds, or five seconds.

In asynchronous mode the event notification occurs immediately and the RefreshTimeout period should not elapse. If, however, the Text adapter is polling for screen text changes, it is possible that the Text adapter could wait the RefreshTimeout period before continuing the automation.

If the delay between setting text and the next automation action is approximately five (5) seconds, then changing the RefreshTimeout property for each of the Text adapter automation components to one (1) second could potentially increase the speed of the automation.

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