I have this issue when i like to use a record

Hi ​@mariano.carames,

You are getting this error from which action?

Mostly this error is happening with the Browser: Run JavaScript action due to issues with the JavaScript in use.

Hi ​@Padmakumar  
I get this error both when running it with js and with the recorder, whether selecting them one by one or recording and having them generated automatically.

Can you share a snippet of these two actions?

This is with Recorder
 

This with JS
 

This is with Recorder
 

This with JS
 

Ok.

1. Recorder: Capture → What is the wait time mentioned in the action for system response? If it is already there as shown below, kindly try after changing the package version. 

2. Browser: Run JavaScript → Since the root cause of the issue can be mainly the given code, please share the JS code that you are using.

1. Recorder: Capture → I have the time set the same as you, at 15 seconds.

2. Browser: Run JavaScript →  document.getElementById('username').value=''
   document.getElementById('password').value=''

Hi ​@mariano.carames , you can use the wait for object and pass that to actually dynamically wait. Also to go into dynamic conditions you can put that action in the while look and in that you can again check so that once it is available it will break out of the loop

Have you tried after changing the Recorder package version?

For the JS action, please try the following:

1. Combine into one-liner

• Try chaining both assignments in one statement:

JavaScriptdocument.getElementById('username').value = 'yourUser'; document.getElementById('password').value = 'yourPass';

       AA handles this better because it’s a single execution block.

2. Add explicit waits before JS
Before the JS action:

• Use Browser: Wait for page to load (e.g., 30–60 seconds).
• Optionally, add a Wait for Condition for username and password.

3. Use Recorder for input

• Instead of JS, use Recorder: Capture to set values in those fields. It’s more reliable because AA uses object-based selectors rather than injecting JS.

4. Wrap JS in AA-supported syntax
Sometimes adding return true; at the end helps:

JavaScriptdocument.getElementById('username').value = 'yourUser';
document.getElementById('password').value = 'yourPass';
return true;

5. Include the problematic Browser: Run Javascript action inside an Error Handler: Try block

• Inside the Error Handler: Catch includes:
  1. Delay action;
  2. The same Browser: Run Javascript action OR use the Recorder package for the same functionality;
• Select the On error, continue with next action checkbox at the Error Handler: Catch action.

      This will ensure any failed attempts will be performed once again to proceed with the bot execution.

This configuration works perfectly for me, thank you very much!

Check it multiple times, as it might go beyond that because of Internet speed, speaking from experience😅