topic Re: Having to clear cache too often for users in Peer-Peer Topics

Having to clear cache too often for users

jasoncrcsd — Thu, 02 May 2024 15:31:58 GMT

We have some users on a MAC where their google classroom submit button dosn't work. The solution seems to be just do the below but it keeps happing. Is there any way of in chrome just having it not keep cache? I think this would cut down 25% of our tickets if we could just have it not maintain the cache to get corrupted.

In Chrome

On your computer, open Chrome .
At the top right, click More. Clear browsing data.
Choose a time range, like Last hour or All time.
Select the types of information you want to remove.
Click Clear data.

Re: Having to clear cache too often for users

npl — Fri, 03 May 2024 09:08:37 GMT

There are two chrome policies that you can apply

ClearBrowsingDataOnExitList

BrowsingDataLifetime

See https://support.google.com/chrome/a/answer/10686330?hl=en&sjid=8485731551023242357-EU for details.

I have used ClearBrowsingDataOnExitList but you may need to apply BrowsingDataLifetime

Re: Having to clear cache too often for users

YERKO — Fri, 03 May 2024 16:39:03 GMT

Saludos @jasoncrcsd nos podrias contar mas acerca del/los equipos en que detectas el problema y/o ticket?

Te cuento que to trabajo con un iMac mediados del 2015 con Os Catalina y el navegador chrome Versión 124.0.6367.92 (que actualizo automaticamente) y nunca he tenido problemas de ese tipo en Classroom. Quizas así vamos descartando equipo, sistema operativo, navegador, usuario hasta encontrar el problema.

Éxito!!

página principalcreación de una tareacomentario en el muro

Re: Having to clear cache too often for users

Kim_Nilsson — Mon, 06 May 2024 08:33:07 GMT

I'm with @YERKO - we have several hundred teachers, only using Mac, and have never heard of the issue you report, @jasoncrcsd - nor have I ever experienced it.

Re: Having to clear cache too often for users

jasoncrcsd — Mon, 06 May 2024 11:18:39 GMT

It seems like we have a constant string of random issues the solution tends to be clearing cache. On more then just the MACS thats just the current excample it happens on the chromebooks too