# Error Model The public-facing error model in Virusis should help users understand what happened without exposing internal implementation details. ## Common Error Families ### Access and session * session expired * access not available for this action * shared link could not be opened ### Processing flow * analysis is still in progress * result is temporarily delayed * the user should try again shortly ### Analysis availability * the input could not be analyzed right now * the input type is not supported in this context * an external dependency may be temporarily unavailable ### Report and result details * file-inspection details are not available for this result * context or enrichment sections are not available for this result * some report sections may appear later than others ### Export and sharing * the report could not be exported * the share link could not be generated * the selected output is not available for this result ## Good language for user-facing errors A safe approach for user-facing error messages is: * do not hide the error * name the technical layer briefly * tell the user the next step when possible Example: messages like "Static analysis result has not been generated yet" follow this pattern well. --- # 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.virusis.com/api-reference/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.