Django Admin not invalidating cache on save

[northkode]

we have a pretty basic config:

CACHEOPS = {
    'auth.user': {'ops': 'get', 'timeout': 60 * 15},
    'auth.*': {'ops': ('fetch', 'get')},
    'auth.permission': {'ops': 'all'},
    'license.*': {'ops': 'all'},
    'users.*': {'ops': 'all'},
    'assessments.*': {'ops': 'all'},
    'trainingplans.*': {'ops': 'all'},
    'questionnaires.*': {'ops': 'all'},
    'workouts.*': {'ops': 'all'},
    'shop.*': {'ops': 'all'},
    'system.*': {'ops': 'all'},
    '*.*': {},
}

and everytime we update something in the admin, the object is still cached via API calls. Is there something I'm missing here?

[Suor]

That's something new. The only idea I have is that cacheops is not setup in admin or is disabled there somehow. Otherwise your will need to debug it.

[northkode]

i'm using out of the box setup based on the readme, yet it says that it should invalidate based on signals and the django admin does signals for saving and editing models.

Not sure what you mean, debug it.. we literally just did a pip install and added it to our configs

[Suor]

By debug I mean, go other how it works: do signals fire? are cacheops handlers called? are redis queries executed? I.e. what is happening at every separate step.

[Suor]

Ok, another thing that comes to mind maybe admin is issuing mass updates or somehow else hit the CAVEATS?