> For the complete documentation index, see [llms.txt](https://docs.wellcomecollection.org/incident-retros/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wellcomecollection.org/incident-retros/2021-09-20_search-not-available.md). # Incident retro - search not available **Incident from:** 2021-09-20 **Incident until:** 2021-09-20 **Retro held:** 2021-09-22 * [Timeline](#timeline) * [Analysis of causes](#analysis-of-causes) * [Actions](#actions) ## Timeline 20 September 2021 See 16.32 Updown alert for: Front End Works Search (Origin) Front End Works Search (Cache) 16.35 DM: I’ve just deployed, but server routing for works is broken. I’ve got the fix and think we should be able to roll forward 16.39 JP yeah tempted to say we roll back for now 16.40 NP put a message about the search issue in #wc-platform-feedback 16.41 DM has a PR 16.43 JP I’ve started a rollback here btw; can’t do any harm even if we get that PR in 16.44 JP But I do think we should wait to check stage before promoting \[the PR fix] 16.45 Updown recovery for: Front End Works Search (Origin) Front End Works Search (Cache) 16.46 NP Okay, looks like I can search again. \[Fixed by the rollback, not the PR] Also said search was working in #wc-platform-feedback ## Analysis of causes A deployment caused server routing for works to break, and end to end tests didn’t catch the problem on stage. ## Actions **DM** * Add render tests for the catalogue app top-level pages [#7063](https://github.com/wellcomecollection/wellcomecollection.org/pull/7063) DONE * Create a runbook for front end incidents **JG** * Investigate why end to end tests didn’t break on all pages --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.wellcomecollection.org/incident-retros/2021-09-20_search-not-available.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.