Serf Query Ack resiliency

One of the use cases, where we dispatch the critical task using query where Serf query propagation is by gossip and response is P2P to the requester. So, resiliency reside in dispatch but not in response/ack. If P2P link is busted, it would lose the ack. Better options to make query ack more resilient ?

(Gossiping back through all nodes would be overkill but option to ack back through subset of nodes)