shared queries not correct across subgraphs

[ha-li]

Hi, I'm getting data that does not match the correct object.
This is the query

   query instrumentSets {
        instrumentSets {
             id
             name createdAt
             dial { 
                 id 
                 handedness
             }
       }
   }

`

But the data I get back is incorrect:

{
   "data": {
       "instrumentSet": [
        {
            "id": "abc",
           "name": "list1"
           ...
            "dial": {
                   "id": "123",
                   "handedness": "left"
            }
        },
        {
            "id": "efg",
           "name": "list2"
           ...
            "dial": {
                   "id": "456",
                   "handedness": "right"
            }
        }
     ]
  }
}

but dials are in the wrong instrument list. list2 should have dial 123, and list2 should have diab 123

I have the following 2 subgraphs: instruments and dials:

instruments.graphqls:

type Query {
    instrumentSet(id: ID): InstrumentSet @shareable
    instrumentSet(filter: JSON, page: Int, size: Int, sortBy: String): [InstrumentSet!] @shareable
}

# this is the full schema for InstrumentSet in InstrumentApplication
type InstrumentSet @key (fields: "id") {
      id: ID!
      name: String!
      createdAt: DateTime
} 

In Application Instruments, no special resolvers needed:

  public class SubGraphSchema 
...
    public GraphQLSchema customSchema() {
          return SchemaParser.newParser()
              .file("instruments.graphqls")
              .resolvers (
                  queryresolver,         // a queryresolver implements getInstrumentSet(String id)
                  mutationresolver)
              .build()
              .makeExecutableSchema();
    }
}

dial.graphqls:

type Query {
    instrumentSet(id: ID): InstrumentSet @shareable
    instrumentSet(filter: JSON, page: Int, size: Int, sortBy: String): [InstrumentSet!] @shareable
    dial(id: ID!) Dial
    dials: [Dial]
}

type InstrumentSet @key (fields: "id") {
    id: ID!
    dial: Dial
}

type Dial {
   id: ID!
   handedness: String 
}

In Application Dial, added a custom resolver for InstrumentSet:

   public class InstrumentSetResolver implements GraphQLResolver<InstrumentSet> {
     public Dial dial(InstrumentSet instrument) {
        // some repository look ups, nothing fancy, eg
        return dialRepository.findByInstrumentSetId(instrument.getId());
    }
  }
  ... 
  public class SubGraphSchema  
    ... 
 
    public GraphQLSchema customSchema() {
          return SchemaParser.newParser()
             .file("dial.graphqls")
             .resolvers ( 
                  queryresolver,          // a query resolver implements queries, those work and are fine
                  mutationresolver)
             .build()
             .makeExecutableSchema();
    }

I can see when I submit the query that both applications begin loading the data immediately, but then when the results are merged into the final output, the data results in dials showing up in the wrong instrument list.

How do I resolve this?