Solved

A360 Task Bot editor crashes when trying to select any variables in a dropdown on any package.


Userlevel 1
Badge +4

I’m seeing issues with any of my task bots when I try to edit a variable.

For instance:

Select package “Text file: Get text”.

When I click on the drop-down for the option to “Save the outcome to a variable” the page becomes unresponsive and eventually crashes.

When clicking to select a variable
A few seconds later.

I’ve tried multiple task bots and restarting my browser.

Clicking the option to create a new variable does not crash, but I already have the variable defined, so this will not work.

icon

Best answer by sleemand 24 April 2024, 15:39

View original

13 replies

Userlevel 6
Badge +16

Hi @sleemand 

Please review the following updates from AA. Downgrade your Chrome version to an older one, specifically version 123.x this should resolve the issue. Also, keep an eye on the following KB for the latest updates

https://apeople.automationanywhere.com/s/article/A360-UI-getting-an-error-code-STATUS-STACK-OVERFLOW-when-clicking-the-drop-down-button-on-the-bot-edit-page

Summary

Following the release of the new Google Chrome Browser version v124.x (124.0.6367.60 or 124.0.6367.61) and Edge browser version v124.x (124.0.2478.51), intermittent problems have been observed when clicking the dropdown button ▼ in the Automation 360 bot editor window on A360.x Control Room versions. Below error pops up "Aw Snap! something went wrong while displaying the website":

Note: The problem may manifest in any Bot Editor window of A360 Control Room when a drop-down is selected.

Cause

Resolution/Workaround

If you encounter this intermittent error, we recommend you to

  1. Clear the browser cache
  2. Restart the browser and retry the UI action.

Until the definitive solution is provided, we advise postponing the upgrade of Google Chrome browser to version 124.x (124.0.6367.60 or 124.0.6367.61) and Edge browser to 124.x (124.0.2478.51).

Additional Information

As Google Chrome version v124.x and Edge version v124.x is introduced this week, we've noticed instances where interactions with UI dropdowns in the Automation 360 bot editor window can trigger the appearance of the Chrome "Aw, Snap!" page, as shown in the attached screenshot. This occurrence obstructs users from completing their intended UI actions, accompanied by the "STATUS_STACK_OVERFLOW" error code.

 
Userlevel 1
Badge +4

Resolution/Workaround

If you encounter this intermittent error, we recommend you to

  1. Clear the browser cache
  2. Restart the browser and retry the UI action.

Until the definitive solution is provided, we advise postponing the upgrade of Google Chrome browser to version 124.x (124.0.6367.60 or 124.0.6367.61) and Edge browser to 124.x (124.0.2478.51).

Additional Information

As Google Chrome version v124.x and Edge version v124.x is introduced this week, we've noticed instances where interactions with UI dropdowns in the Automation 360 bot editor window can trigger the appearance of the Chrome "Aw, Snap!" page, as shown in the attached screenshot. This occurrence obstructs users from completing their intended UI actions, accompanied by the "STATUS_STACK_OVERFLOW" error code.

 

Hello, thanks for the details. However, this is not possible for us.

Our browser updates are maintained by corporate group policies to happen automatically.

 

Is this same issue present in Firefox? I could possibly use that in the meantime.

Userlevel 6
Badge +16

Hi @sleemand

Firefox might work give it a try. 

Userlevel 1
Badge +4

So far, Firefox is working if anyone else is running into the same situation as I am.

Firefox version 125.0.2, just installed today.

Userlevel 6
Badge +16

Great @sleemand 

Badge

Can we get an update from support about a long term fix for this issue?  Our company doesn’t permit Firefox and Chome/Edge updates are managed and installed when they’re released.  We can try to roll back the install, but that will not be an acceptable permanent solution, so management is requesting an ETA for the long term fix.  Thanks.

Userlevel 1
Badge +4

 @andrew123 

I discovered this article today, which may help if you are able to adjust Chrome/Edge flags.

https://support.google.com/chrome/thread/270094591/err-connection-reset-in-google-chrome-web-browser-only?hl=en

The TLS1.3 change is affecting other websites for me as well.

This change seems to have fixed the issue for me in Edge.

Badge

 @andrew123 

I discovered this article today, which may help if you are able to adjust Chrome/Edge flags.

https://support.google.com/chrome/thread/270094591/err-connection-reset-in-google-chrome-web-browser-only?hl=en

The TLS1.3 change is affecting other websites for me as well.

This change seems to have fixed the issue for me in Edge.

Hello, good morning my friend, I'm trying make it, but don't work in Browser Chrome.

Badge

Install the extension in your browser to fix this issue. This is a workaround.

https://github.com/santanbarnwal/Chrome-drop-down-Bug-workaround

Badge +3

Install the extension in your browser to fix this issue. This is a workaround.

https://github.com/santanbarnwal/Chrome-drop-down-Bug-workaround

thx man!

Badge

only two option is there 

 

1.downgrade your browser

2.AA360 team will update 

 

 

Userlevel 3
Badge +7

Hi @sleemand, @ChanduMohammad, @Santan.B, @kwertie, @miguelroman, @Joseph Raja, @andrew123 

 

You can try following method till there is a permanent fix to this.

To regain access to the Control Room UI, refresh your browser. Navigate to the desired dropdown using keystrokes (TAB, SHIFT-TAB) without clicking on the problematic dropdown. Then, utilize the UP-DOWN arrows to make your selection.

or if policy allows 
 

Run below script in your browser console after you login to your automation anywhere instance. This will remove error for this session  
=================================================================
function removeAriaOwnsAttribute(element) {if (element.hasAttribute('aria-owns')) {         element.removeAttribute('aria-owns');     } } function mutationCallback(mutationsList, observer) {    mutationsList.forEach(mutation => {             removeAriaOwnsAttribute(mutation.target);     }); } const observer = new MutationObserver(mutationCallback); observer.observe(document.documentElement, {     attributes: true,     childList: true,     subtree: true,     attributeFilter: ['aria-owns'] });             ================================================================

 

or download the extension from
https://github.com/santanbarnwal/Chrome-drop-down-Bug-workaround

 

Userlevel 3
Badge +5

I have shared the issue history, workaround and the latest update that fixes the issue.

 

Reply