- This topic has 2 replies, 3 voices, and was last updated 17 hours, 41 minutes ago by
.
- You must be logged in to reply to this topic.
-
Posts
-
A fresh browser every morning is basically introducing itself to those dashboards as a new device over and over again. With several scheduled jobs, keeping profiles, browser processes and restarts under control on your own machine can also turn into a separate job. Take a few minutes to read how browser as a service works here: https://gologin.com/blog/browser-as-a-service/ . Then check whether the provider lets you reconnect to the same browser profile or session between runs rather than launching a clean one each time. For this kind of automation, that persistence matters a lot more than how quickly the first browser window starts.
Those verification prompts can show up even when the cookies are still valid, because some sites remember a lot more about the browser than just the login cookie. Local storage, IndexedDB and the browser profile itself can all matter when the site decides whether it recognizes the device. Use a persistent Playwright context with the same userDataDir for every scheduled run and keep that profile between jobs. That usually gives the site a much more consistent browser identity than exporting cookies and rebuilding everything from scratch each morning.
I have been building a small automation tool that logs into a few business dashboards and collects reports every morning. The scripts work fine when I run them manually, but I’m having trouble keeping the login sessions consistent between scheduled runs. Sometimes everything goes through without a problem, while other times the websites ask for verification codes or treat the browser like a completely new device. I’ve tried saving cookies with Playwright, but that hasn’t solved it for every site. A colleague suggested moving the browser itself to a cloud service rather than starting a fresh Chromium instance for each job. I’m not entirely sure how that would work or whether it would actually help with session persistence. Has anyone tried this approach? How do you keep browser automation logged in reliably when the scripts run on a schedule?
