Close popover
Mangesh Walhe (Mangesh Walhe)
Sr. System Architect
Pegasystems Inc.
Mangesh Walhe Member since 2018 15 posts
Posted: August 6, 2018
Last activity: April 6, 2019

'Another Handler' error sometimes halts the automation, sometimes doesn't


I have checked the past post closely related to this error (, but the issue I have been facing is slightly different.

I have 2 occuerrences of the 'Another handler already registered for messages from process XXXX' error.

Older occurrence was when a given Webadapter was started to launch an external WebApp and the target process (IEXPLORE.EXE) is attached to WindowsProcess object. This error used to halt the automation completely.

The recent one is when link between WaitForCreate(WFC) of a webpage and pause that is on the True port of WFC is executed. This time it allows the automation to run without any problem. (Refer the attached error_DoesntStopAutomation.txt for error log).

I know that Runtime allows the show to run with few exceptions that it can ignore exceptions, and halts the execution in case of an unignorable error. My question is how is that decision made, especially when its the same kind of error?

(Will upload error log snippets for both errors shortly)

***Edited by Moderator Marissa to update SR Details***

Robotic Process Automation Support Case Created
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.