Skip to content

Data service and network errors

Errors from data service, network and Substreams package lookups.

Each error below is identified by the code in the error response. The response's docsUrl links to the matching entry on this page.

product_code_invalid

Invalid product code · HTTP 400 Bad Request

The product code is not in a valid format.

What to do: Use a product code from your organization's product list, such as rpc, subgraphs or substreams.

product_code_required

Product required · HTTP 400 Bad Request

The request does not name a product.

What to do: Choose the product the API key is for.

product_not_supported

Product not available · HTTP 400 Bad Request

The product does not exist or is not currently available.

What to do: Choose one of the products listed for your organization.

products_list_failed

Products could not be loaded · HTTP 500 Internal Server Error

GraphOps hit an unexpected error while loading the products available to your organization.

What to do: Retry the request. If the error continues, contact support.

substreams_package_catalog_unavailable

Substreams package list unavailable · HTTP 503 Service Unavailable

GraphOps could not load the list of Substreams packages.

What to do: Retry later. You can still open a specific package release by its name and version.

substreams_package_invalid

Substreams package could not be read · HTTP 422 Unprocessable Content

The release was downloaded from the registry, but GraphOps could not read it as a Substreams package. Published releases never change, so the release stays unreadable.

What to do: Check that you entered the right package and version, or choose another release.

substreams_package_not_found

Substreams package release not found · HTTP 404 Not Found

The registry has no published release with this package name and version, or the version is not an exact release, such as latest.

What to do: Check the package name and version on substreams.dev, and use an exact release version.

substreams_package_redirect_rejected

Substreams package download rejected · HTTP 503 Service Unavailable

The registry redirected the package download in a way GraphOps does not follow, such as to an insecure address.

What to do: Retry later. If the error continues, contact support with the package name and version.

substreams_package_timeout

Substreams package download timed out · HTTP 503 Service Unavailable

The registry did not return the package release in time.

What to do: Retry later. If the error continues, contact support with the package name and version.

substreams_package_too_large

Substreams package too large · HTTP 422 Unprocessable Content

The package release is larger than the explorer can inspect. Published releases never change, so the explorer can't open this release.

What to do: Inspect this release locally instead, for example with the substreams CLI.

substreams_package_unavailable

Substreams package unavailable · HTTP 503 Service Unavailable

GraphOps could not load the package release from the registry.

What to do: Retry later. If the error continues, contact support with the package name and version.

Last updated