GraphQL Limitation - Total records

Ask us anything How do I?
1

Hi everyone! I’m facing an issue with my GraphQL query in Supabase that I can’t figure out.

I have approximately 7,600 records in my table, but when I run this query:

query Step1 {
  correlation_5sCollection(first: 1000) {
    pageInfo {
      hasNextPage
      endCursor
    }
    edges {
      node {
        ts
        pair1
        pair1_symbol
        strategies_id
      }
    }
  }
}

I’m only getting 30 items back in total, even though I’m requesting 1,000.

Does anyone know why this is happening or how I can retrieve all the records? Has anyone encountered this before?

Thanks in advance!

2

Hey @bbalint0918 :waving_hand:

Thanks for the detailed screenshots and context, that really helps.​

From what you shared, the issue seems to be that the GraphQL layer (or WeWeb’s data handling) is capping how many records are returned per request, so you only ever get ~30 items even though Supabase reports ~7,600 in total. This is likely a combination of a server‑side page size limit plus the fact that only the first page of results is being fetched, without looping through pagination using pageInfo and endCursor.​

To confirm where the limit lives, a useful next step would be to run the same query in an external GraphQL client and see if you can retrieve more than 30 records there with first: 1000 ; if that works, then the constraint is on the WeWeb side and would need either a paginated fetch pattern or an adjustment to how the collection is configured.