> ## Documentation Index > Fetch the complete documentation index at: https://rocketyard.dev/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > These Actors run on the Apify platform and charge per result. Call one with POST https://api.apify.com/v2/acts/rocketyard~/run-sync-get-dataset-items and the header Authorization: Bearer , or connect Apify's MCP server at https://mcp.apify.com?tools=rocketyard/. # Rocketyard error codes > What each error item code from a Rocketyard Actor means, whether a retry helps, and what to do. Error items are never charged. When an input URL produces no data, a Rocketyard Actor stores one **error item** for it instead of skipping it silently. Error items are never charged. The `error` object follows [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) (Problem Details): `type` links to a section below, `title` names the problem, `detail` explains this occurrence, `instance` is the URL that failed, `status` is the site's HTTP status when there was one, and `code` repeats the code for filtering. ```json theme={null} { "url": "https://example.com/private/report", "input": "example.com/private/report", "error": { "type": "https://rocketyard.dev/errors#robots-disallowed", "title": "Blocked by robots.txt", "detail": "https://example.com/private/report is disallowed by the site's robots.txt, so it was not fetched.", "instance": "https://example.com/private/report", "code": "ROBOTS_DISALLOWED" } } ``` ## Robots disallowed `ROBOTS_DISALLOWED`: Blocked by robots.txt. The site's robots.txt does not allow automated access to this URL (or to the page it redirects to), so it was not fetched. * **Retry helps:** no * **What to do:** Use a page of the site that robots.txt allows, or ask the site owner to allow it. ## Robots unreachable `ROBOTS_UNREACHABLE`: robots.txt unavailable. The site's robots.txt could not be loaded because of a server or network error. Under RFC 9309, the page is then not fetched. * **Retry helps:** yes * **What to do:** Run it again later. ## Private address `PRIVATE_ADDRESS`: Private network address refused. The URL, or a redirect from it, points to a private or local network address. Only public websites are fetched. * **Retry helps:** no * **What to do:** Use a public URL. ## Not found `NOT_FOUND`: Not found. The page or source does not exist (HTTP 404 or 410). * **Retry helps:** no * **What to do:** Check the URL or name. The page may have been removed. ## Blocked `BLOCKED`: Access refused by the site. The site refused access (HTTP 401, 403 or 429) or answered with a bot-check or consent page instead of the content. * **Retry helps:** sometimes * **What to do:** Run it again later or with a different Apify Proxy group. The Actors never log in or solve CAPTCHAs. ## Http error `HTTP_ERROR`: HTTP error. The site answered with another HTTP error: a server error (5xx) that persisted after retries, or an unexpected 4xx status. * **Retry helps:** sometimes * **What to do:** Run it again later. If it persists, the site may be down or the URL may be wrong. ## Timeout `TIMEOUT`: Request timed out. The site did not answer in time, even after retries. * **Retry helps:** yes * **What to do:** Run it again later, or lower Max concurrency for slow sites. ## Network error `NETWORK_ERROR`: Network error. The connection failed (DNS, TLS or a reset connection), even after retries. * **Retry helps:** yes * **What to do:** Check that the domain exists, then run it again later. ## Wrong content type `WRONG_CONTENT_TYPE`: Unexpected content type. The URL returned something the Actor doesn't read, such as a PDF or image instead of an HTML page, or a web page where an API response was expected. * **Retry helps:** no * **What to do:** Use the kind of URL the Actor asks for in its input. ## Too large `TOO_LARGE`: Response too large. The response exceeded the size limit (10 MiB for web pages, 48 MiB for API responses). * **Retry helps:** no * **What to do:** Use a more specific URL. ## Parse error `PARSE_ERROR`: Response could not be read. The response could not be read (malformed HTML or JSON). * **Retry helps:** sometimes * **What to do:** Run it again later. If it persists, open an issue with the URL. ## No structured data `NO_STRUCTURED_DATA`: No structured data found. The page loaded but has none of the data the Actor extracts: no schema.org data (JSON-LD or microdata), or, for the Shopify Actor, no public Shopify catalog on the site. * **Retry helps:** no * **What to do:** Use a detail page (for example a product page rather than a category page), turn on crawling to find detail pages, or for Shopify use a store on Shopify's standard storefront. ## Empty `EMPTY`: Nothing published. The source has nothing to return right now: a list with no open items, a store or collection with no products, a search with no results, or a web page whose HTML has no readable text (often a page built only by JavaScript in the browser). * **Retry helps:** no * **What to do:** Check back later, or use a page whose content the server sends in its HTML. ## No matches `NO_MATCHES`: Nothing matched the filters. The source has items, but none of them matched your filters. * **Retry helps:** no * **What to do:** Loosen the filters. ## Video unavailable `VIDEO_UNAVAILABLE`: Video unavailable. The video is private, removed, age-restricted or otherwise not available without signing in. * **Retry helps:** no * **What to do:** Check the video link. The Actors never sign in, so these videos cannot be read. ## Channel not found `CHANNEL_NOT_FOUND`: Channel not found. No public channel exists at this handle, ID or URL. * **Retry helps:** no * **What to do:** Check the spelling of the handle or channel ID. Still stuck? See [Contact](https://rocketyard.dev/contact.md) and include the run ID and the error item. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.