# Case Errors ### Definition If, during the evaluation of a [case](/guides/glossary/case.md), the processing of [rules](/guides/glossary/rules.md) hits a roadblock, Case Errors gives you an exact overview of where things went wrong. This helps to quickly solve the issue in atfinity's configuration, or refer the exact error to an administrator. ### Overview Case Errors shows you directly in which case something went wrong, what and when happened, and give you a description of the reason for the error. The screen could look like this: ![](/files/-MYEfqy_78c5Zs5P4bVF) | Field | Description | | ----- | ------------------------------------------------------------- | | Time | Date when the error occurred. | | Case | The number of the case in which atfinity has found the error. | | Error | A description of what went wrong. | ### Example Common errors are typos in a condition, missing [information](/guides/glossary/information.md) that's required for an action to be executed, or trying to perform an impossible action on pieces of information, for example subtracting two pieces of information type string. ``` p is Person p.domicile + 1 ``` Trying to add '1' to a person's domicile is impossible. If this is written in a condition, the error will appear in Case Errors. --- # 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://docs.atfinity.io/guides/troubleshooting/case-errors.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.