When I set up a very simple workflow to help log in to the browser interface, I type into the account secret and click submit. After clicking step by step, the flow page of the operation page will appear in the window on the right. But it flashed back immediately after the operation was completed. I added a daley 1h. After not flashback, it was not synchronised on my browser.
Im not sure i fully understood the setup, but i think what you’re seeing might be the robot opening its own browser session instead of using yours. That window is separate from your normal browser, so the login happens there and doesnt show up in the one you have open, and it closes as soon as the run finishes, wich would explain both things you described
if you want it to work on the browser you already have open, open the page manually first and in Use Application/Browser set it to attach to the existing window instead of launching a new one, i think the property is Open Browser set to Never or IfNotOpen depending on your version
can you tell if that window on the right is being launched by the automation itself, or is it your own browser? and are you running this from Studio Web or desktop Studio? that would help narrow it down
It looks like the browser is not fully loaded after clicking the Submit button. Instead of using a long Delay, try using Check App State and wait for the next page or element to appear.
Also, increase the Timeout if needed. This should help keep the UiPath workflow synchronized with the browser.
@_ZHANG_QIONGWEN It sounds like the automation may be working with a different browser/session than the one you are checking manually.
A few things you can verify:
- Make sure all the login activities are inside the same Use Application/Browser activity.
- If you want UiPath to work with an already opened browser, configure Use Application/Browser to attach to the existing browser window instead of opening a new one.
- Check whether the browser is being opened in a separate automation profile/session. In that case, changes made by the automation will not necessarily appear in your normal browser session.
- Adding a long Delay will only keep the workflow running; it will not synchronize two different browser sessions.
- After clicking Submit, add a Check App State or Element Exists activity for an element that is available only after successful login. This is better than using a fixed Delay and will also confirm whether the login actually succeeded.
If the page appears briefly and then closes, also check whether the browser/application is configured to close when the Use Application/Browser activity ends.
Hi @_ZHANG_QIONGWEN ,
You can use the below steps:
- Use Attach Browser / Use Application-Browser to keep UiPath attached to the correct browser tab.
- After clicking Submit, use Check App State, Wait for Element Appear, or On Element Appear instead of a long Delay.
- Set Click activity → WaitForReady = Complete.
- If a new tab/window opens after login, indicate the new browser window and continue automation there.
- Enable Simulate Click or Chromium API input mode for better browser synchronization.
- Avoid using Delay 1 hour. Delays do not synchronize the browser; they only pause the robot.
- Add a Retry Scope if the page takes time to load after login.
Hi @_ZHANG_QIONGWEN,
It looks like the workflow is finishing before the browser page has enough time to load or sync properly.
Try adding a short delay or, better, a Wait for Element after clicking Submit instead of a 1-hour delay.
Also, make sure the workflow is still attached to the correct browser tab/window after the login step.
Let me know if you have any further questions
Could you try adding a Use Application/Browser activity and keep all login actions inside it? Also check whether the browser is being closed by a Close Application/Browser activity or by the execution settings.