> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/operate/v1/data-consumer/support-and-changes.md). # Raise issues and track changes You depend on products other people own, so two operating habits matter: knowing how to get help and not being surprised when a product you rely on changes. ## Get support * **Find the owner.** Every product names its owner and members in the **Contacts** section of its page in the Data Product Hub. That is who to contact for access, clarification, or a problem. * **Raise issues.** When quality or freshness looks wrong, a column is masked that you need, or a number does not reconcile, contact the owner with specifics: the product, the metric or column, what you expected, and what you saw. You are often the first to notice a problem downstream. * **Request changes or access** through the same channel. A new dimension, a broader grant, or a fix is a request to the owner, who decides and (for access) leaves an audited grant. ## Stay ahead of changes A product evolves, and some changes affect you: * **Follow products you depend on.** Following a product keeps you aware of its health and changes, and signals adoption to the owning team. * **Watch for version and breaking changes.** When an owner bumps a version or announces a breaking change (a dropped column, a changed grain, a renamed measure), check whether your reports, models, or queries depend on what changed, and update before the change lands. * **Re-validate trust after a change.** Re-check the product's quality and freshness signals (see [Trust and monitor](/operate/v1/data-consumer/trust-and-monitor.md)) before trusting outputs built on the new version. ## The relationship Think of it as a contract between you and the owner: they keep the product healthy, documented, and forewarn breaking changes (see [Operate your product](/operate/v1/data-developer/operate-your-product.md) in the Developer section); you read the trust signals, consume within the governance, and report problems early. That two-way discipline is what makes a shared product dependable. --- # 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://v2.dataos.info/operate/v1/data-consumer/support-and-changes.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.