Graph Indexer Issue

[oselezi]

I'm getting a issue after closing allocations. I'm not sure if it's related to the new operator because I've changed it

    deployment: {
      "bytes32": "0xbbde25a2c85f55b53b7698b9476610c3d1202d88870e66502ab0076b7218f98a",
      "ipfsHash": "Qmaz1R8vcv9v3gUfksqiS9JUz7K9G8S5By3JYn8kTiiP5K"
    }
    receipt: "7cb078fb62f040350ed46b62235c3991b7f12f4500000000000000000000000000000000000000000000000000002d79883d2000a3376f8e6472de3867232bb47a4bd5c5ea937bd891a998b6110d76b95d3da9cb3c8029ab510809e4ff5a236140c9b25cd42920439260b94206b9da6bfed7f1810a04741d18c0ee95ede731ddc0ed9c1c"
[2021-10-13 18:50:39.701 +0000] ERROR (IndexerService/1 on indexer-service-56b8447df8-ln6s8): Failed to handle paid query
    indexer: "0xb06071394531B63b0bac78f27e12dc2BEaA913E4"
    operator: "0x7A361DB89c9419699DEf3349b5F6F1cBA294267D"
    component: "Server"
    err: {
      "type": "IndexerError",
      "message": "Failed to process paid query",
      "stack":
          IndexerError: Failed to process paid query
              at Object.indexerError (/opt/indexer/packages/indexer-common/dist/errors.js:139:12)
              at /opt/indexer/packages/indexer-service/dist/server/index.js:213:50
              at Generator.throw (<anonymous>)
              at rejected (/opt/indexer/packages/indexer-service/dist/server/index.js:6:65)
      "code": "IE032",
      "explanation": "https://github.com/graphprotocol/indexer/blob/master/docs/errors.md#ie032",
      "cause": {
        "type": "Error",
        "message": "Unable to sign the query response attestation",
        "stack":
            Error: Unable to sign the query response attestation
                at QueryProcessor.<anonymous> (/opt/indexer/packages/indexer-service/dist/queries.js:60:31)
                at Generator.next (<anonymous>)
                at fulfilled (/opt/indexer/packages/indexer-service/dist/queries.js:5:58)
        "status": 500
      }
    }
    ```
Now I'm pointing directly to the thegraph endpoint to avoid my network subgraph but I'm getting the same error
but some queries run well and others bad. Not all queries.