Follow

Troubleshooting Automation Issues

Sometimes issues related to automations may result in Context Not Found (CNF) and other errors. The following article provides an overview of troubleshooting processes for these types of issues.

 

Weak Controls & Missing Connections

 

When an automation results in a CNF, begin troubleshooting it as you would any other error. Review the strength of the controls on the automated page to ensure they are being properly recognized by Capriza. Also review the automation connections. Is an automation set to “Page loads from some connections” when it should be set to “Page loads from any connection.” Refer to the article Errors: Common Causes & How to Avoid Them for more information.

 

Automation Delays

 

When an automation executes, the Capriza Engine fully loads the page and executes the click or other action on behalf of the user. To give the source application time to properly load, Capriza adds a default delay of 50 milliseconds (ms) between the initiation of the automation and the execution of the action. Slower source application may require you to increase this delay to ensure the control is actionable.


To increase the default delay value, open the Automations dialog to the relevant automation and open the Options menu. “Delay” will be set to 50 ms. Enter a new value and save your changes.

 

 

 

Click Execution

 

If a click automation is not registering despite properly configured controls and delays, changing the type of click used by the Capriza Engine may alleviate the issue. By default, the click is optimized to reduce unnecessary delays but if you encounter race conditions with the click or other issues, you may want to change the type of click to be user emulated. To change this setting, click the wrench icon to open the Web Properties dialog and navigate to the “Properties” tab.

 

 

Open the Advanced properties section. Two options are included for “Click execution”: Optimized (default) and User emulated (which imitates the button press and release of an end user.

 

 

Change to “User emulated” and close the dialog.

 

Text Input Method

 

If a text input automation is failing (e.g. enter X value) and all controls, connections, and delays are configured properly, try changing the text input method. Similar to Click execution, this option is found under Advanced Properties in the Properties tab of the Web Properties dialog. Three options are provided:

  • Paste: Default option. This pastes the entire value at once for optimal performance.
  • Keyboard: Simulates a user typing in the value.
  • Paste without focus

Change to “Keyboard” and close the dialog.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.