# Common Issues This section outlines the HTTP status codes returned by Drizz Public APIs. Each code reflects the state of the request ranging from successful triggers to validation issues, conflicts, or service-level errors. These responses enable engineering, QA, and CI/CD systems to programmatically detect failures, apply retries, escalate integration issues, and maintain predictable automation workflows. #### 1. App with Package Name Not Found * App not registered in Drizz * Package name mismatch * Organization access issue #### 2. Test Plan Not Found * Invalid test plan ID * Test plan archived or deleted * Cross-organization access attempt #### 3. File Size Exceeded * APK exceeds 500 MB * Optimize APK using build tools #### 4. Invalid Access Token * Token expired (24-hour validity) * Incorrect client credentials Missing or malformed x-api-key header --- # 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.drizz.dev/drizz-api-integration/common-issues.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.