When one website keeps returning to a sign-in page or shows an old preference, clearing all browser data is a broad experiment. A reset limited to that website is easier to understand and leaves unrelated sessions out of the test.

Save work before removing local data

Finish or copy any unsaved form text and check whether the web app holds offline work locally. Confirm that you can sign back into the account, including any required second factor. If the page is part of a managed business service, record the error and check with its support contact before deleting potentially useful local work.

In Chrome Settings, open Privacy and security, Third-party cookies, then See all site data and permissions. Search for the website’s name, inspect the matching address and delete only the intended entry. Read the confirmation rather than selecting every similar-looking domain.

Repeat the same task

Open the website through an address you already trust, sign in again and repeat the operation that failed. Check the actual outcome, such as opening the expected document, instead of stopping at the welcome screen. Cookies can preserve sign-in and preferences, so being asked to authenticate again is an expected consequence of this test.

If the failure remains, note that a scoped data reset did not resolve it. Possible next evidence includes the exact error, affected account and whether another approved browser has the same problem. Do not repeatedly delete more data without a reason.

Some services use separate sign-in and application domains. An unresolved problem does not justify allowing every third-party cookie globally. Follow the service’s documented requirements or ask its administrator to identify the necessary scope.

Source: Google Chrome Help.