I am working with an automation for a web based app. After certain time the session of the app ends and this makes the robot to fail, I identified this end session message but I don´t know where and how to include it in the automation as the session can end in any part of the automation, making it to fail so far. To you have any ideas on how I can handle this event?
Thanks in advance for your help
***Updated by moderator: Lochan to add SR details***
***Edited by Moderator Marissa to close comments***
If the session can end at any time, then it will be challenging to code for. Your strategy might be to have a separate event that detects the event that it is triggered when the session ends, and re-stores the session to its prior location. In your automations, whenever you navigate, you might need to allow sufficient time during any waits for this restore process to occur. This all depends on how the session ends and is restored. If the session only ends at the beginning, then you might only need to handle it in one place. If it can end during a navigation from one screen to another, then you'll need to know how it is restored. I would suggest you document the various steps required and what exactly happens when the session fails to help you come up with the best method to handle it.
Thank your for your idea. Indeed the session can end at any time. I have two more questions I hope you could help me with:
1. If a create an event that detect when the session ends, how to do I "pause" the automation wherever it was executing, re start the app and continue again in the same point?
2. I am working on a different project with a web page that's presenting a similar behaviour. It seems that because of the concurrence of the web app, sometime the web page freezes at any moment without any reason and Pega is not showing any error at all. I implemented wait for create, try-cath, breakpoints, but the automation never went through that. It is important to mentioned that in the day to day, the business unit experience this and the way they handle this is that they re start Internet Explorer. The problem is Pega is not giving us any error so we don´t know how to identify this event. I am attaching the runtime log of the latest execution. Please read from line Info | 11:16:19.776 a. m. | 16 | MTA | Automation | MAN_SolicitudApertura
1. You can't really pause the automation. If you were navigating from Page A to Page B, you could use a WaitAny to detect Page B or Page Session End and take the action there. Assuming the Page Session end allows you to re-login and then resumes from the same Page B with all of your data present, then you could simply increase your Page B WaitForCreate time. The event would trigger your automation to log you in while the original automation is waiting for it.