[BUG]: Clear scheduledBatchTimer will cause query lost when batchesByKey has multiple keys

[yar2001]

Intended outcome:
Persisted Queries should retry when it meet PersistedQueryNotFound message (when works with HTTP batch)

Actual outcome:
The Persisted Queries does not retry because the timer will be clear by new schedule with different key.

How to reproduce the issue:
The bug is obvious in source code, when Persisted Queries start a retry using batch schedule timeout, and some other normal query also schedule with a new key, the old timeout will lost.

Versions

System:
OS: Linux 5.19 Debian GNU/Linux bookworm/sid
Binaries:
Node: 18.7.0 - /usr/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 8.19.2 - /usr/bin/npm
Browsers:
Firefox: 102.3.0esr
npmPackages:
@apollo/client: ^3.7.0 => 3.7.0

[yar2001]

Seems the bug is caused by this commit.
When isFirstEnqueuedRequest is true, the timeout should not be cleared. Maybe more clear code and corresponding test should be added

[yar2001]

Hello, I think it is a bug easy to fix but has serious effects, will you @benjamn take a look?

[yar2001]

The problem seems to be solved since I haven't met the Persisted Queries problem again.

[github-actions]

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Client usage and allow us to serve you better.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
For general questions, we recommend using StackOverflow or our discord server.