Skip to content

Multiple top-level queries do not work for unhealthy subgraphs #2744

Open
@leoyvens

Description

@leoyvens

Do you want to request a feature or report a bug?
bug

What is the current behavior?
This query:

{
  factories(first: 5, subgraphError:allow) {
    id
  }
  _meta(subgraphError:allow) {block {number}}
}

Returns:

{
  "data": {
    "_meta": {
      "block": {
        "number": 1001380
      }
    }
  },
  "errors": [
    {
      "message": "indexing_error"
    }
  ]
}

Which is missing the factories field. But if the _meta query is removed, the factories are returned.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
On a subgraph with non-fatal errors that is unhealthy, attempt to query more than one top-level field.

What is the expected behavior?
All top-level fields are included in the response.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions