There is no single Buda login lifetime for every site. The AI browser runs in the Agent's cloud computer, but the website controls its own cookies, session expiry and reauthentication rules. A new Buda chat Session is not the same thing as a fresh login to that website; similarly, waking the cloud computer does not promise that a site session is still valid. Changes to the browser profile or the site's security policy can also require a new login.

For a scheduled dashboard check, test the exact site once after the cloud computer has slept and once from a new Buda Session. In the task instruction, require the Agent to check it reached the dashboard before reading metrics. If it sees a sign-in screen, MFA prompt or access-denied page, it should stop, record that no dashboard data was collected, and report “login required” through the delivery channel you configured; it should not treat the login page as a zero-valued report. Use scheduled-task history to review the run and reauthenticate interactively when needed. Do not put passwords or one-time codes into the task prompt.

Which dashboard and sign-in method are you using? A site with short-lived SSO or MFA may need a different integration path from a site with a long-lived browser session.