Reactor groupBy: What happens with remaining items after GroupedFlux is canceled?

I need to group infinite Flux by key with high cardinality.

For example:

1. group key is domain url
2. calls to one domain should be strictly sequential (next call happens after previous one is completed)
3. calls to different domains should be concurrent
4. time interval between items with same key (url) is unknown, but expected to have burst nature. Several items emitted in short period of time then long pause until next group.

queue
    .groupBy(keyMapper, groupPrefetch)
    .flatMap(
       { group ->
           group.concatMap(
               { task -> makeSlowRemoteCall(task) },
               0
           )
           .takeUntil { remoteCallResult -> remoteCallResult == DONE }
           .timeout(groupTimeout, Mono.empty())
           .then()
       }
      , concurrency
    )

I cancel the group in two cases:

1. makeSlowRemoteCall() result indicates that with high probability there will be no new items in this group in near future.

2. Next item is not emitted during groupTimeout. I use timeout(timeout, fallback) variant to suppress TimeoutException and allow flatMap's inner publisher to complete successfully.

I want possible future items with same key to make new GroupedFlux and be processed with same flatMap inner pipeline.

But what happens if GroupedFlux has remaining unrequested items when I cancel it?

Does groupBy operator re-queue them into new group with same key or they are lost forever. If later what is the proper way to solve my problem. I am also not sure if I need to set concatMap() prefetch to 0 in this case.