> For the complete documentation index, see [llms.txt](https://developer.siteminder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.siteminder.com/smx-api/additional-resources/reference-tables/error-warning-types.md). # Error Warning Types (EWT) Defines types of warnings that accompany specific errors.

Code	Name	Reason
1	Unknown	Indicates an unknown error.
2	No implementation	Indicates that the target business system has no implementation for the intended request.
3	Biz rule	Indicates that the XML message has passed a low-level validation check, but that the business rules for the request message were not met.
4	Authentication	Indicates the message lacks adequate security credentials.
5	Authentication timeout	Indicates that the security credentials in the message have expired.
6	Authorization	Indicates the message lacks adequate security credentials.
7	Protocol violation	Indicates that a request was sent within a message exchange that does not align to the message.
8	Transaction model	Indicates that the target business system does not support the intended transaction-oriented operation.
9	Authentical model	Indicates the type of authentication requested is not recognized.
10	Required field missing	Indicates that an element or attribute that is required in by the schema (or required by agreement between trading partners) is missing from the message.
11	Advisory
12	Processing exception	Indicates that during processing of the request that a not further defined exception occurred.
13	Application error	Indicates that an involved backend application returned an error or warning, which is passed back in the response message.

--- # 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://developer.siteminder.com/smx-api/additional-resources/reference-tables/error-warning-types.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.