Already Login to ACME - Automation Skips Login Page After First Successful Run

Help Action Center
,
1

Hi everyone,

After running my automation process for the first time, it successfully logged into the ACME website and completed the intended tasks. However, when I try to run the automation again, it doesn’t navigate to the login page since I’m already logged in from the previous session. This causes an error because the workflow is still trying to execute the login process.

How can I adjust my automation to handle the scenario where the user is already logged in and skip the login steps if necessary?

Any suggestions would be greatly appreciated!

Thanks in advance!

2

Hi @mohammed.fuseini

Use Check App State Activity and indicate thhe Home Page screen of ACME website.

In Target Appears do nothing and in Target Does not Appears keep the activities like type into to type the Username, Password and click the Login button.

Regards

1 Like
3

@mohammed.fuseini,

Refer this Sample Project.
CalculateClientSecurityHash.zip (3.1 MB)

In this project refer this workflow.

The image displays a file directory with a list of .xaml files under the "System1" folder, with "System1_Login.xaml" circled in red. (Captioned by AI)

Logic is available in it.

Thanks,
Ashok :slight_smile:

1 Like
4

Hie @mohammed.fuseini if you are working with modern activity use check app state activity and if you are still working with classic activity use element exist activity to check if the page is logged in or loged out … this help you to handle this error problem
cheers Happy Automation

1 Like
5

@mohammed.fuseini

If you are using the Classic activity then use element exist like
→ if the acme home page exist skip the login if not then login to the acme again.

If you are using the modern activity then use check app state(which is similar to the element exists in classic activity)
→ if the acme home page exist skip the login if not then login to the acme again.

1 Like
6

Thank you! @vrdabberu

7

This was very helpful. Thank you @ashokkarale

1 Like
8

I used Check App state and it worked. Thank you for you contribution

9

Thank you @naveen.s. I used Check App State and it worked

10

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.