- πΊπΈUnited States keithdoyle9 Pennsylvania, USA
Has this ever been resolved? We're running into the same error.
- πΊπΈUnited States papagrande US West Coast
@keithdoyle9, this ended up being a problem with too many cache tags on that client's page. Oddly, Cloud Next was worse than Cloud Classic when using the acquia_purge module.
I solved it by removing the individual cache tags with the
getCacheTagsToInvalidate()
method on the custom entity. The entities are populated and displayed as a complete group so individual entity tags aren't needed.However, the problem remains in the module in that it shouldn't have a fatal error.
- πΊπΈUnited States cgmonroe
Added a possible work around to prevent this to the issue description.
I know this is possible because I have used onKernelResponse events to modify CacheableResponse response's CacheMetadata for other things.