# Subgraph errors Source: https://docs.graphops.xyz/platform/errors/subgraphs Each error below is identified by the `code` in the [error response](/platform/errors#error-response). The response's `docsUrl` links to the matching entry on this page. ## `managed_subgraph_already_following` Already following a Subgraph ID · HTTP 409 Conflict This Managed Subgraph already follows a Graph Network Subgraph ID, so it can't follow another one. **What to do:** Change its target type to Deployment CID first, then change it to the Graph Network Subgraph ID you want it to follow. ## `managed_subgraph_bound_aliases` Endpoint Aliases still target it · HTTP 409 Conflict One or more Endpoint Aliases still target this Managed Subgraph, so it can't be deleted. **What to do:** Delete those Endpoint Aliases or change them to Deployment CID targets, then delete the Managed Subgraph again. ## `managed_subgraph_cid_invalid` Invalid Deployment CID · HTTP 422 Unprocessable Content The Deployment CID is malformed. A Deployment CID starts with `Qm` and has 46 characters. **What to do:** Check the Deployment CID and enter it again without extra spaces or characters. ## `managed_subgraph_cid_is_current` Next CID matches Current CID · HTTP 409 Conflict The Deployment CID you chose for the upgrade is the Managed Subgraph's Current version. **What to do:** Enter the Deployment CID of the new version you want to prepare. ## `managed_subgraph_compatibility_superseded` Schema comparison out of date · HTTP 409 Conflict The schema comparison for the Next version was made against a Current version that has since changed, so the promotion was not applied. **What to do:** Refresh the Managed Subgraph, review the new schema comparison and promote again. ## `managed_subgraph_conflict` Managed Subgraph changed · HTTP 409 Conflict The Managed Subgraph changed while your request was being applied, so the request was not applied. **What to do:** Refresh the Managed Subgraph and try again. ## `managed_subgraph_create_failed` Managed Subgraph not created · HTTP 500 Internal Server Error GraphOps hit an unexpected error while creating the Managed Subgraph. **What to do:** Check the list of Managed Subgraphs before retrying, in case it was created. If the error continues, contact support. ## `managed_subgraph_credits_required` Credits required · HTTP 403 Forbidden Your organization has no available credits, so GraphOps can't start new managed indexing, such as creating a Managed Subgraph, starting an upgrade or promoting a version. **What to do:** Add credits in Billing, then try again. Automatic top-ups help avoid this in future. ## `managed_subgraph_current_changed` Current version changed · HTTP 409 Conflict The Current version changed after the upgrade was checked, so the check no longer applies to the version that serves queries. **What to do:** Start the upgrade again so GraphOps checks the next version against the new Current version. ## `managed_subgraph_current_missing` Current version missing · HTTP 409 Conflict GraphOps could not find a Current version for this Managed Subgraph. **What to do:** Contact support with the Managed Subgraph's name and the time of the request. ## `managed_subgraph_deletion_requested` Deleted Managed Subgraph · HTTP 409 Conflict This Managed Subgraph has been deleted, so it can't be renamed. **What to do:** Create a new Managed Subgraph if you need one with this name. The name is free once removal finishes. ## `managed_subgraph_deprovisioning` Previous version still being removed · HTTP 409 Conflict This Deployment CID was a previous version of the Managed Subgraph and is still being removed, so it can't be prepared again yet. **What to do:** Wait for removal of the previous version to finish, then start the upgrade again. ## `managed_subgraph_limit_reached` Managed Subgraph limit reached · HTTP 409 Conflict Your organization has reached its Managed Subgraph limit. Paused Managed Subgraphs and those being removed still count toward it. **What to do:** Delete a Managed Subgraph you no longer need and wait for its removal to finish, or contact support to raise the limit. ## `managed_subgraph_manifest_fetch_failed` Manifest unavailable · HTTP 503 Service Unavailable GraphOps could not retrieve the manifest for this Deployment CID. The deployment may not exist, may not be available yet, or the request timed out. **What to do:** Check that the Deployment CID is correct and has been deployed, then retry. ## `managed_subgraph_manifest_invalid` Invalid manifest · HTTP 422 Unprocessable Content The deployment's manifest is too large, is missing a required field or has an invalid value. The error message names the field. **What to do:** Fix the manifest, deploy a new version and use its Deployment CID. ## `managed_subgraph_manifest_invalid_yaml` Manifest is not valid YAML · HTTP 422 Unprocessable Content The content at this Deployment CID is not a valid YAML Subgraph manifest. **What to do:** Check that the Deployment CID identifies a Subgraph deployment rather than another file, such as its schema. ## `managed_subgraph_manifest_multi_network` Manifest uses several networks · HTTP 422 Unprocessable Content The deployment's data sources and templates declare more than one network. A Subgraph must use one network. **What to do:** Deploy a version that uses one network across all data sources and templates, and use its Deployment CID. ## `managed_subgraph_name_exists` Name already in use · HTTP 409 Conflict Another Managed Subgraph in your organization already uses this name, ignoring case. A deleted Managed Subgraph keeps its name until removal finishes. **What to do:** Choose a different name, or wait for the deleted Managed Subgraph's removal to finish. ## `managed_subgraph_network_following` Versions follow a Subgraph ID · HTTP 409 Conflict This Managed Subgraph follows a Graph Network Subgraph ID, so its versions come from that ID and you can't start, cancel or promote upgrades yourself. **What to do:** To manage versions yourself, change its target type to Deployment CID first. ## `managed_subgraph_network_mismatch` Subgraph ID uses another network · HTTP 400 Bad Request The current version of the Graph Network Subgraph ID uses a different network from this Managed Subgraph. **What to do:** Choose a Graph Network Subgraph ID whose current version uses the Managed Subgraph's network. ## `managed_subgraph_network_unsupported` Network not supported · HTTP 422 Unprocessable Content The deployment uses a network that managed indexing does not support. **What to do:** Choose a deployment on a supported managed indexing network. The Subgraphs networks page lists them. ## `managed_subgraph_next_blocked` Next version waiting to start · HTTP 409 Conflict The Next version can't be promoted because it is waiting for indexing to start. **What to do:** Wait for the Next version to start indexing and become ready, then promote it. ## `managed_subgraph_next_cancel_failed` Upgrade not cancelled · HTTP 500 Internal Server Error GraphOps hit an unexpected error while cancelling the upgrade. **What to do:** Refresh the Managed Subgraph and retry. If the error continues, contact support. ## `managed_subgraph_next_must_be_cancelled` Upgrade in progress · HTTP 409 Conflict This Managed Subgraph has a Next version, so it can't be deleted. **What to do:** Cancel the upgrade first. If it follows a Graph Network Subgraph ID, change its target type to Deployment CID instead, which retires the Next version. ## `managed_subgraph_next_network_mismatch` Next version uses another network · HTTP 400 Bad Request The next deployment uses a different network from this Managed Subgraph. **What to do:** Choose a deployment that uses the Managed Subgraph's network. The error message names it. ## `managed_subgraph_next_not_attached` Next version not ready to serve · HTTP 409 Conflict The Next version can't be promoted because it is not ready to serve queries yet. **What to do:** Wait for the Next version to show Ready to promote, then promote it. ## `managed_subgraph_next_not_converged` Next version still being prepared · HTTP 409 Conflict The Next version can't be promoted because it is still being prepared. **What to do:** Wait for the Next version to show Ready to promote, then promote it. ## `managed_subgraph_next_not_healthy` Next version not healthy · HTTP 409 Conflict The Next version can't be promoted because it is not healthy. **What to do:** Read the Next version's status explanation. If it reports a Subgraph error, fix it and start an upgrade with a corrected version. ## `managed_subgraph_next_not_ready` Next version not ready · HTTP 409 Conflict The Next version is not ready to promote. **What to do:** Check the Next version's status, and promote it once it shows Ready to promote. ## `managed_subgraph_next_not_synced` Next version still syncing · HTTP 409 Conflict The Next version can't be promoted because it is still catching up with the network head. **What to do:** Wait for the Next version to finish syncing and show Ready to promote, then promote it. ## `managed_subgraph_next_occupied` Upgrade already in progress · HTTP 409 Conflict This Managed Subgraph already has a Next version with a different Deployment CID. **What to do:** Promote or cancel the current upgrade before starting one with another deployment. ## `managed_subgraph_next_stage_failed` Upgrade not started · HTTP 500 Internal Server Error GraphOps hit an unexpected error while starting the upgrade. **What to do:** Refresh the Managed Subgraph to check whether the upgrade started, then retry. If the error continues, contact support. ## `managed_subgraph_next_status_unavailable` Upgrade status unavailable · HTTP 409 Conflict GraphOps could not confirm the Next version's current status, so it can't check that the version is ready to promote. **What to do:** Refresh the Managed Subgraph and try again. If the status stays unavailable, contact support. ## `managed_subgraph_next_validation_failed` Next deployment check failed · HTTP 500 Internal Server Error GraphOps hit an unexpected error while checking the next deployment. **What to do:** Retry the check. If the error continues, contact support. ## `managed_subgraph_not_active` Managed Subgraph not active · HTTP 409 Conflict Only an active Managed Subgraph can be upgraded. This one is paused or being removed. **What to do:** If managed indexing paused because your credits ran out, add credits to resume it, then try again. Otherwise, contact support. ## `managed_subgraph_not_found` Managed Subgraph not found · HTTP 404 Not Found No Managed Subgraph with this ID exists in the organization. **What to do:** Check the Managed Subgraph ID and that you selected the organization that owns it. ## `managed_subgraph_plan_required` Monthly plan required · HTTP 403 Forbidden Managed Subgraphs need a monthly plan, and your organization doesn't have one. **What to do:** Ask an owner or billing admin to choose a monthly plan in Billing, then create the Managed Subgraph again. ## `managed_subgraph_promotion_conflict` Managed Subgraph changed · HTTP 409 Conflict The Managed Subgraph changed since you last loaded it, for example because another version was promoted or its target type changed, so the request was not applied. **What to do:** Refresh the Managed Subgraph, review its versions and try again. ## `managed_subgraph_promotion_failed` Promotion failed · HTTP 500 Internal Server Error GraphOps hit an unexpected error while promoting the Next version. **What to do:** Refresh the Managed Subgraph to check whether the promotion happened, then retry. If the error continues, contact support. ## `managed_subgraph_read_failed` Managed Subgraph not loaded · HTTP 500 Internal Server Error GraphOps hit an unexpected error while loading the Managed Subgraph. **What to do:** Refresh the page or retry the request. If the error continues, contact support. ## `managed_subgraph_rename_failed` Managed Subgraph not renamed · HTTP 500 Internal Server Error GraphOps hit an unexpected error while renaming the Managed Subgraph. **What to do:** Refresh the Managed Subgraph and retry. If the error continues, contact support. ## `managed_subgraph_schema_backfill_conflict` Current version changed · HTTP 409 Conflict The Current version changed while GraphOps prepared its schema for the upgrade check. **What to do:** Refresh the Managed Subgraph and start the upgrade again. ## `managed_subgraph_schema_backfill_mismatch` Current schema can't be verified · HTTP 409 Conflict GraphOps could not verify the Current version's schema, so it can't compare an upgrade with it. **What to do:** Contact support with the Managed Subgraph's name and the Deployment CID you want to upgrade to. ## `managed_subgraph_schema_fetch_failed` Schema unavailable · HTTP 503 Service Unavailable GraphOps could not retrieve the query schema that the deployment's manifest references. **What to do:** Retry the request. If the error continues, check that the deployment's schema file was uploaded with it. ## `managed_subgraph_schema_invalid` Invalid query schema · HTTP 400 Bad Request The deployment's query schema is too large or is not a valid Subgraph schema. **What to do:** Fix the schema, deploy a new version and use its Deployment CID. ## `managed_subgraph_state_change_failed` State not changed · HTTP 500 Internal Server Error GraphOps hit an unexpected error while changing the Managed Subgraph's state, such as deleting it. **What to do:** Refresh the Managed Subgraph to check whether the change was applied, then retry. If the error continues, contact support. ## `managed_subgraph_target_invalid` One target required · HTTP 400 Bad Request The request must include exactly one target: a Deployment CID or a Graph Network Subgraph ID. **What to do:** Send either `deploymentHash` or `subgraphId`, not both and not neither. ## `managed_subgraph_tracking_failed` Target type not changed · HTTP 500 Internal Server Error GraphOps hit an unexpected error while changing the Managed Subgraph's target type. **What to do:** Refresh the Managed Subgraph to check its target type, then retry. If the error continues, contact support. ## `managed_subgraph_tracking_membership_required` Current version not published to ID · HTTP 400 Bad Request The Managed Subgraph's Current version is not one of the versions published to this Graph Network Subgraph ID. **What to do:** Publish the Current version to the Subgraph ID first, or choose the ID it was published to. ## `managed_subgraph_tracking_requires_current` Can't follow a Subgraph ID yet · HTTP 409 Conflict A Managed Subgraph can only follow a Graph Network Subgraph ID while it is active and has no Next version. **What to do:** Promote or cancel the upgrade first. If the Managed Subgraph is paused, resume it before changing its target type. ## `managed_subgraph_validation_failed` Deployment check failed · HTTP 500 Internal Server Error GraphOps hit an unexpected error while checking the deployment for a new Managed Subgraph. **What to do:** Retry the check. If the error continues, contact support. ## `managed_subgraphs_disabled` Managed Subgraphs unavailable · HTTP 503 Service Unavailable Managed Subgraphs are not available right now, so GraphOps can't check or create one. **What to do:** Contact support if you need managed indexing. ## `managed_subgraphs_list_failed` Managed Subgraphs not listed · HTTP 500 Internal Server Error GraphOps hit an unexpected error while listing your organization's Managed Subgraphs. **What to do:** Refresh the page or retry the request. If the error continues, contact support. ## `public_catalog_pagination_invalid` Invalid discovery page · HTTP 400 Bad Request The Subgraph discovery request has a negative offset or a page size outside 1 to 100. **What to do:** Send a whole-number `offset` of 0 or more and a `limit` from 1 to 100. ## `public_query_rate_limited` Explorer query allowance used · HTTP 429 Too Many Requests Your organization has used its free deployment explorer queries for this hour, or free explorer queries are paused until the next UTC day. **What to do:** Retry after the time in the `Retry-After` header, or query the Subgraph through your own endpoint, which uses your organization's normal billing. ## `public_subgraphs_graphql_failed` Unreadable Graph Network response · HTTP 503 Service Unavailable The Graph Network returned a response that GraphOps could not read, so the request could not be completed. **What to do:** Retry the request. If the error continues, contact support. ## `public_subgraphs_indexers_unavailable` No indexer could answer · HTTP 503 Service Unavailable No indexer on The Graph Network could answer the query for this deployment right now. **What to do:** Retry the request after a short wait. If the error continues, choose another deployment. ## `public_subgraphs_indexing_failed` Indexers report an indexing error · HTTP 422 Unprocessable Content Every indexer serving this deployment reports an indexing error, so The Graph Network can't answer queries for it. **What to do:** Check whether the Subgraph has a newer version. Otherwise choose another deployment, or ask its publisher to fix and redeploy it. Retrying the same deployment does not clear the error. ## `public_subgraphs_inventory_invalid` Discovery catalog unavailable · HTTP 503 Service Unavailable GraphOps found inconsistent data in the Subgraph discovery catalog and could not return it. **What to do:** Retry later. If the error continues, contact support. ## `public_subgraphs_no_allocations` No indexer serving the deployment · HTTP 409 Conflict No indexer on The Graph Network is currently serving this deployment, so it can't be queried. **What to do:** An Owner or Developer can import it as a Managed Subgraph if its network is supported, or choose another deployment. The same request succeeds only after an indexer starts serving the deployment. ## `public_subgraphs_quota_unavailable` Explorer allowance unavailable · HTTP 503 Service Unavailable GraphOps could not check your organization's free deployment explorer query allowance. **What to do:** Retry the query after a short wait, or query the Subgraph through your own endpoint. ## `public_subgraphs_request_failed` Discovery request failed · HTTP 503 Service Unavailable GraphOps hit an unexpected error while loading Subgraph discovery or the deployment explorer. **What to do:** Retry the request. If the error continues, contact support. ## `public_subgraphs_schema_invalid` Served schema unreadable · HTTP 503 Service Unavailable GraphOps could not read the schema that indexers serve for this deployment. **What to do:** Retry the request. If the error continues, choose another deployment or contact support. ## `public_subgraphs_upstream_failed` Graph Network unreachable · HTTP 503 Service Unavailable GraphOps could not reach The Graph Network, or the request timed out. **What to do:** Retry the request after a short wait. If the error continues, contact support. ## `public_subgraphs_upstream_unavailable` Graph Network unavailable · HTTP 503 Service Unavailable The Graph Network returned an error instead of an answer to the request. **What to do:** Retry the request after a short wait. If the error continues, contact support. ## `subgraph_alias_changed` Endpoint Alias changed · HTTP 409 Conflict The Endpoint Alias's serving version changed while your update was being applied, so the update was not applied. **What to do:** Refresh the Endpoint Alias and make the change again. ## `subgraph_alias_cid_invalid` Invalid Deployment CID · HTTP 400 Bad Request The Deployment CID is malformed. A Deployment CID starts with `Qm` and has 46 characters. **What to do:** Check the Deployment CID and enter it again without extra spaces or characters. ## `subgraph_alias_create_failed` Endpoint Alias not created · HTTP 500 Internal Server Error GraphOps hit an unexpected error while creating the Endpoint Alias. **What to do:** Check your Endpoint Aliases before retrying, in case it was created. If the error continues, contact support. ## `subgraph_alias_delete_failed` Endpoint Alias not deleted · HTTP 500 Internal Server Error GraphOps hit an unexpected error while deleting the Endpoint Alias. **What to do:** Check your Endpoint Aliases to see whether it was deleted, then retry. If the error continues, contact support. ## `subgraph_alias_exists` Endpoint Alias already exists · HTTP 409 Conflict Your organization already has an Endpoint Alias with this name. **What to do:** Choose a different name, or change the target of the existing Endpoint Alias. ## `subgraph_alias_invalid` Invalid Endpoint Alias name · HTTP 400 Bad Request The Endpoint Alias name is invalid. Names use 1 to 63 lowercase letters, numbers and hyphens, and start and end with a letter or number. **What to do:** Choose a name that follows these rules. The error message says which rule the name breaks. ## `subgraph_alias_managed_target_invalid` Managed Subgraph target unavailable · HTTP 400 Bad Request The Managed Subgraph target is not available to this Endpoint Alias. It doesn't exist in your organization, has been deleted, or has no Current version. **What to do:** Choose an active Managed Subgraph in this organization as the target. ## `subgraph_alias_manifest_fetch_failed` Manifest unavailable · HTTP 503 Service Unavailable GraphOps could not retrieve the manifest for this deployment. The deployment may not exist, may not be available yet, or the request timed out. **What to do:** Check that the Deployment CID or Graph Network Subgraph ID is correct, then retry. ## `subgraph_alias_manifest_invalid` Invalid manifest · HTTP 422 Unprocessable Content The deployment's manifest is too large, is missing a required field or has an invalid value. The error message names the field. **What to do:** Choose another deployment, or fix the manifest and deploy a new version. ## `subgraph_alias_manifest_invalid_yaml` Manifest is not valid YAML · HTTP 422 Unprocessable Content The content at this Deployment CID is not a valid YAML Subgraph manifest. **What to do:** Check that the Deployment CID identifies a Subgraph deployment rather than another file, such as its schema. ## `subgraph_alias_manifest_multi_network` Manifest uses several networks · HTTP 422 Unprocessable Content The deployment's data sources and templates declare more than one network. A Subgraph must use one network. **What to do:** Choose a deployment that uses one network across all data sources and templates. ## `subgraph_alias_not_found` Endpoint Alias not found · HTTP 404 Not Found No Endpoint Alias with this name exists in the organization. **What to do:** Check the Endpoint Alias name and that you selected the organization that owns it. ## `subgraph_alias_schema_invalid` Invalid query schema · HTTP 400 Bad Request The deployment's query schema is not a valid Subgraph schema, so GraphOps can't show its details. **What to do:** Choose another deployment, or fix the schema and deploy a new version. ## `subgraph_alias_target_invalid` One target required · HTTP 400 Bad Request The request must include exactly one Endpoint Alias target: a Deployment CID, a Graph Network Subgraph ID or a Managed Subgraph. **What to do:** Send exactly one of `deploymentHash`, `subgraphId` or `managedSubgraphId`. ## `subgraph_alias_update_failed` Endpoint Alias not updated · HTTP 500 Internal Server Error GraphOps hit an unexpected error while updating the Endpoint Alias. **What to do:** Refresh the Endpoint Alias to check its target, then retry. If the error continues, contact support. ## `subgraph_aliases_list_failed` Endpoint Aliases not listed · HTTP 500 Internal Server Error GraphOps hit an unexpected error while listing your organization's Endpoint Aliases. **What to do:** Refresh the page or retry the request. If the error continues, contact support. ## `subgraph_deployment_hash_invalid` Invalid Deployment CID · HTTP 400 Bad Request The Endpoint Alias's Deployment CID target is malformed. A Deployment CID starts with `Qm` and has 46 characters. **What to do:** Check the Deployment CID and enter it again without extra spaces or characters. ## `subgraph_deployment_not_found` Deployment not available · HTTP 404 Not Found The deployment explorer can't open this deployment. It isn't used by your organization's Managed Subgraphs or Endpoint Aliases, and isn't an available published version in Subgraph discovery. **What to do:** Check the Deployment CID or Graph Network Subgraph ID, and open the deployment from Subgraph discovery or your organization's Subgraphs. ## `subgraph_id_invalid` Invalid Subgraph ID · HTTP 400 Bad Request The Graph Network Subgraph ID is malformed. A Subgraph ID has 43 or 44 characters. **What to do:** Check the Graph Network Subgraph ID and enter it again without extra spaces or characters. ## `subgraph_metadata_failed` Deployment details not loaded · HTTP 500 Internal Server Error GraphOps hit an unexpected error while loading the deployment's details. **What to do:** Retry the request. If the error continues, contact support. ## `subgraph_network_fetch_failed` Graph Network lookup failed · HTTP 503 Service Unavailable GraphOps could not look up this Graph Network Subgraph ID's versions on The Graph Network. **What to do:** Retry the request after a short wait. If the error continues, contact support. ## `subgraph_network_metadata_failed` Subgraph ID details not loaded · HTTP 500 Internal Server Error GraphOps hit an unexpected error while loading the Graph Network Subgraph ID's details. **What to do:** Retry the request. If the error continues, contact support. ## `subgraph_network_not_configured` Subgraph ID targets unavailable · HTTP 503 Service Unavailable Graph Network Subgraph ID targets are not available for Managed Subgraphs right now. **What to do:** Use a Deployment CID target instead, or contact support. ## `subgraph_network_observation_superseded` Subgraph ID lookup out of date · HTTP 409 Conflict GraphOps received older Graph Network data for this Subgraph ID than it has already recorded, so the update was not applied. **What to do:** Retry the update after a short wait. ## `subgraph_network_subgraph_deprecated` Subgraph ID has no active version · HTTP 404 Not Found This Graph Network Subgraph ID has no active version on The Graph Network. **What to do:** Use another Graph Network Subgraph ID, or the Deployment CID of the version you want. ## `subgraph_network_subgraph_not_found` Subgraph ID not found · HTTP 404 Not Found This Graph Network Subgraph ID was not found on The Graph Network. **What to do:** Check the Graph Network Subgraph ID, or use the Deployment CID of the version you want. ## `subgraph_query_invalid` Invalid query · HTTP 400 Bad Request The deployment explorer query is not valid GraphQL or does not match the deployment's schema. The error message lists each problem with its line and column. **What to do:** Fix the problems listed and run the query again. ## `subgraph_query_operation_required` Operation name required · HTTP 400 Bad Request The deployment explorer query defines several operations and none was chosen, or it has no operation with the chosen name. **What to do:** Choose the operation name to run, or check its spelling. ## `subgraph_query_operation_unsupported` Only queries can run · HTTP 400 Bad Request The deployment explorer only runs query operations, not mutations or subscriptions. **What to do:** Run a `query` operation instead. ## `subgraph_query_response_too_large` Query result too large · HTTP 422 Unprocessable Content The query result is larger than the deployment explorer returns. **What to do:** Request fewer entities or fields, for example with a smaller `first`, and run the query again. ## `subgraph_query_too_deep` Query nested too deeply · HTTP 400 Bad Request The deployment explorer query nests fields more deeply than the explorer allows. **What to do:** Reduce the nesting of the query, or split it into several queries. ## `subgraph_query_too_large` Query too large · HTTP 400 Bad Request The deployment explorer query is larger than the explorer allows. **What to do:** Shorten the query, or split it into several queries.