# Error Case In general `` supports the same tags as ``. But there are limitations. ## No forward-to-endpoint Placing `` inside `` is not supported, as this would require “auto increment” numbers to be assigned even in the case of `` (as any arbitrary endpoint might be called, which might require them). It is an explicit design goal to only support auto-increment numbers (e.g. for invoice numbers) in the case of ``. ## Limited Support of Variables On error the same tags can be used as for ``, but placeholders for client generated parameter values are not supported. An error might have happened during parameter transformation, and therefore client generated parameters are not necessarily available. {% hint style="info" %} **Limited Support of Variables** This limitation not only applies to the use of placeholders in the endpoint-definition, but also for any data-source or XSLT used within a transformation. {% endhint %} System generated parameters may be used. In addition, for the processing of the \ tag the following additional parameters are available: * `${internal-error-text}` - This contains an internal error message. It is important this is not exposed to any end customer, as it might contain security-sensitive information such as “cannot connect to database at IP address 1.2.3.4” etc. * `${parameter-transformation-error-text}` - In case the request failed because the parameter transformation failed, and a message was set in the `` tag in its output. --- # Agent Instructions: 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: ``` GET https://onestopconcept.gitbook.io/open-endpoints/configuration/types-of-endpoints/error-case.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.