Why does the Splunk forwarder stop after a network gap, and how can we prevent this from happening for temporary network issues?

There was a network gap while splunk was forwarding the data: HTTPClient - Invalid URI deployment.server.com:8089 because Temporary failure in name resolution the question is, why does Splunk stop and does not keep trying when the DNS started working normally again. Splunk was in a stopped state until started manually. Is there any token that can be changed to make Splunk not stop for temporary network issues? Thanks.