cancel
Showing results for 
Search instead for 
Did you mean: 

Doubt regarding the exception

NivedN
Level 3
Hi Blueprism community, 

I need a help 

While learning the wait stage using centrix data solutions i am facing an issue like this 

**Internal : AMI error occurred in Wait Start Stage 'login window is there?' on page 'Login' - Not Connected**

Here is my workflow
37011.png


Here when the login window is present it is not throwing any exception, but when the login window is absent, it is showing a pop up like this 
37012.png


I am wondering why it is happening eventhough i had put put the exception block there 


Can anyone helps to resolve the issue

@Denis__Dennehy  can u help me 
1 BEST ANSWER

Best Answers

HarshitRawat
Level 8
Hi Nived,
This is a very obvious error and something to be careful of when designing the flows

Any application should be first launched by BP before it can start working on it

When the application is not already launched and wait stage tries to find the window , it would show this error

The reason is that Business Object is not connected to the application yet. hence BP can't identify the application details
So you first need to launch the application before you start working on it

also what you are calling as Exception block is just an exception stage.
An exception stage doesn't catch exception but actually it generates exception.

Recover and Resume are the stages which catch and neutralize exception.
In your current flow an error is already occurring before the timeout can happen

Hope this helps 🙂

View answer in original post

2 REPLIES 2

HarshitRawat
Level 8
Hi Nived,
This is a very obvious error and something to be careful of when designing the flows

Any application should be first launched by BP before it can start working on it

When the application is not already launched and wait stage tries to find the window , it would show this error

The reason is that Business Object is not connected to the application yet. hence BP can't identify the application details
So you first need to launch the application before you start working on it

also what you are calling as Exception block is just an exception stage.
An exception stage doesn't catch exception but actually it generates exception.

Recover and Resume are the stages which catch and neutralize exception.
In your current flow an error is already occurring before the timeout can happen

Hope this helps 🙂

BenLyons
Staff
Staff
Hi Nived,

As per Harshit's response, this will have occurred where the application was either launched manually or via a different object.

If the launch action is in this object, then ensure you use this when launching the application for further testing/development work.

If the launch action is in a different object, then this action should start with an attach page (not stage). It's best practice to have an attach page in every object that doesn't contain a launch action. This page will contain a read stage that read's the base part of the application to check "Is Connected?".

Then use a decision so that if it's not connected you can use a navigate stage to attach. If it's already connected then the page can end. (see below). Add this as a page stage at the start of every action.

37008.png
37009.png
37010.png
Ben Lyons Senior Product Specialist - Decipher SS&C Blue Prism UK based