Wojciech Trocki yes, essentially that is what will happen. If you look at the link below [1] you can see they say that if the same operation comes back down the chain with an error then onError will ignore it.

This makes it difficult to complete this ticket in a clean and low cost manner. I have done some investigation and written the code to perform this logic but in the process discovered that we cannot use onError for this purpose because of [1].

The other options we have here are to build our own link which uses onError as well but tracks the operations in some other manner, i.e. another list in the cache. In my opinion this is bad because it introduces a huge amount of corner cases such as tracking multiple simultaneous operations and the cleanup involved with these operations once they have been accepted by the server as conflict free. This paired with the fact that the use case for this in a production application is not very clear to me means I am not sure we should progress this. I would be happy to talk further about this, what do you think Dara Hayes and Wojciech Trocki?

[1] https://github.com/apollographql/apollo-link/tree/master/packages/apollo-link-error#retrying-failed-requests