Getting Exception in Production for few transactions

[SagarPhadtare]

Hi, We are in production now & running multiple cases everyday. I am getting "Could not identify process owning the current foreground window" for few cases. Ratio of these errors are very few like 2%. I have increased the wait time for this element but I guess this is nothing to do with wait time. Not sure why it is throwing exception. Can anyone please help me. Thanks, Sagar

[Denis__Dennehy]

Hello Sagar, You are not giving us much information to go on there. Where exactly in your solution are you getting this error, what type of stage, what type of application, what type of element?

[SagarPhadtare]

Hi Denis, Application - Web application Stage - Navigate Where exactly in your solution are you getting this error - In Object layer

[Denis__Dennehy]

Hello Sagar, There is a module in the learning area of the portal about getting the kind of information required to help with an issue. My guess is that you have not built your process based upon a process template - which would have best practice exception handling in. If best practice exception handling is incorporated what your process should be doing when this very occassional issue occurs is catching the error, tidying up the application (which may involve restart it), renavigating to where it needs to be, and trying again. It will do this retry loop a few times before letting the exception bubble up to your main page. This retry exception handling logic tends to fix occassional system errors like what you describe - for more details there is an Exception Handling guide on the portal, instructions distributed with the Process Template, and an example process in the Lifecycle Orientation training.

[Denis__Dennehy]

Hello Sagar, There is a module in the learning area of the portal about getting the kind of information required to help with an issue. My guess is that you have not built your process based upon a process template - which would have best practice exception handling in. If best practice exception handling is incorporated what your process should be doing when this very occassional issue occurs is catching the error, tidying up the application (which may involve restart it), renavigating to where it needs to be, and trying again. It will do this retry loop a few times before letting the exception bubble up to your main page. This retry exception handling logic tends to fix occassional system errors like what you describe - for more details there is an Exception Handling guide on the portal, instructions distributed with the Process Template, and an example process in the Lifecycle Orientation training.