- This topic has 1 reply, 1 voice, and was last updated 20 hours, 3 minutes ago by
.
- You must be logged in to reply to this topic.
-
Posts
-
I’ve 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?
I’ve 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?
