> For the complete documentation index, see [llms.txt](https://engineering.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.umh.app/engineering/development-process/how-to-decide-what-to-build/signals/error-reporting.md). # Error reporting What our product tells us when something goes wrong, and who acts on it. Owner: Jeremy Where an error goes depends on who has to act on it: the person running the system sees it in the product, and a programming error goes to [Sentry](https://docs.sentry.io/). [Error management](/engineering/development-process/how-to-build/coding-standards/architecture/error-management.md) says how to decide while you write the code. Every error belongs to a [home ticket](/engineering/development-process/how-to-build/tickets.md). ## Rules * An error reaches its owner through its `feature` tag, which names the home ticket it belongs to. That ticket's owner acts on it. * An error with no `feature` tag waits in [Triage](/engineering/development-process/how-to-decide-what-to-build/signals/triage.md), which gives it a home ticket and adds the tag. * A home ticket has no more errors than its [stability target](/engineering/development-process/how-to-build/tickets/rollout.md#success) allows, during the rollout and after it. * An error nobody has to act on is a defect in the source. [Error management](/engineering/development-process/how-to-build/coding-standards/architecture/error-management.md) says what to change in the code. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://engineering.umh.app/engineering/development-process/how-to-decide-what-to-build/signals/error-reporting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.