Skip deferred fragments in collectFields only when same label is used

[robrichard]

For this case:

query HeroNameQuery {
  hero {
    ...TopFragment @defer(label: "DeferTop1")
    ...TopFragment @defer(label: "DeferTop2")
  }
}
fragment TopFragment on Hero {
  name
}

Currently the second spread of TopFragment gets skipped by the visited fragment check and the result is:

[
  {
    data: { hero: {} },
    pending: [
      { id: '0', path: ['hero'], label: 'DeferTop1' }
    ],
    hasNext: true,
  },
  {
    hasNext: false,
    incremental: [{ id: '0', data: { name: 'Luke' } }],
    completed: [{ id: '0' }],
  },
]

I think this will be an issue for clients. Since no pending is sent for the fragment with the DeferTop2 label, clients will assume this fragment has been inlined (not deferred), but the necessary fields have not been included in the initial result.

This PR updates the visited fragment check to only skip deferred fragments that have already been collected with the same label, while still preventing infinite loops from circular fragment references

New response:

[
  {
    data: { hero: {} },
    pending: [
      { id: '0', path: ['hero'], label: 'DeferTop1' },
      { id: '1', path: ['hero'], label: 'DeferTop2' },
    ],
    hasNext: true,
  },
  {
    hasNext: false,
    incremental: [{ id: '0', data: { name: 'Luke' } }],
    completed: [{ id: '0' }, { id: '1' }],
  },
]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
graphql-js	Ignored	Preview	Jul 22, 2026 3:51pm