[Bug] Side TOC does not work for navigation

[Naarcha-AWS]

What do you want to do?

• Request a change to existing documentation
• Add new documentation
• Report a technical problem with the documentation
• Other

Tell us about your request. Provide a summary of the request and all versions that are affected.

Browser version: Firefox 115.5.0esr

When selecting certain pages on the side TOC in production, it redirects me back to the home page, as shown in the following recording:

Screen.Recording.2023-12-12.at.12.38.23.PM.mov

In my local instance, the side TOC works fine. I also tried clearing my cache, but the bug persisted. Could this be a redirect or Jekyll config issue? Do we need to clear our memory on the backend?

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

[ohltyler]

+1, I was seeing this when trying to visit https://opensearch.org/docs/latest/search-plugins/search-pipelines/index/. Although the direct links to 2.11 were working as expected. I am using Chrome. It seemed to be transient and resolved after a minute or two.

[AMoo-Miki]

Based on the timestamp of the video and the logs, I believe the site was accessed while edge cache invalidation was going on. When the build process triggers this action, it doesn't wait for it to complete and simply moves on. In the past, when we didn't have as much content, the invalidation would complete by the time the build pipeline completed but nowadays, the invalidation completes roughly 5 mins after the pipeline completes. If the website is accessed during that time, a request could randomly fail and the failure would be cached in the browser for a minute or two (which is what Tyler observed).

We have 3 options (bad to good):

1. Accept that this duration will progressively increase and that deployment pipeline ending is not the end of the action.
2. Create a mechanism to check for the completion of cache invalidation; this would prevent giving the wrong sense of completion when things are still happening.
3. Use a hosting stack that works better for us.

Over the past couple of years, our content has evolved, our needs have changed, and we have learned that we need features that our current hosting platform cannot offer. I would love to switch our hosting stack.

However, until then, this is a known limitation.

[hdhalter]

#7185