Drupal Cache Issues

[eric-gade]

Description

We appear to have some issues with Drupal caching template data on our location routes. Specifically, this seems to emerge whenever there has been an error along one of those routes in our live environments. Once the source of the error is gone (through code changes or API updates), the environment's page will still display the error, even though we cannot reproduce locally.

Logging into the live machine and clearing the Drupal cache manually has made the problem go away, which indicates that we have some kind of caching issue we don't fully understand. (See example thread here)

With #2115, we have disabled caching on all point and location routes. This is not ideal; we will need some kind of short-lived caching when we hit IoC scale, in order to better serve pages in high-trafficked areas. This ticket is a spike and possibly implementation ticket for figuring out how to set reasonable TTLs on a given route, and to investigate how these templates/errors are being cached in a pre-2155 world.

Acceptance criteria

• Have explored how/why point location pages with errors are being cached erroneously in the pre-#2155 setup
• Have figured out how to cache specific routes with a specific TTL, or have come up with some other caching strategy.