service deregister suddenly

I am currently utilizing Consul version 1.10.3 in conjunction with various microservices built on .NET Core. Occasionally, I encounter an issue where a service deregisters abruptly and then re-registers itself. During these instances of service deregistration, I execute connectivity and probe health check commands between the microservices and Consul, and they appear to be functioning correctly. Is there a configuration setting within the config.json file that dictates the duration of service deregistration?

Start with Consul 1.10.3 service registration and health-check behavior, focusing on the config.json settings related to deregistration. Compare the observed connectivity and probe results with the service's registration and health-check lifecycle. Done means identifying the cause or confirming the relevant deregistration-duration setting and documenting the required configuration.

Written by the indexing model from the issue text.