This is due to either high number of simulanous request when gsa ser taking all the cpu so few moments will skip some requests and show didnt respond, and sometimes due to cb cant solve recaptcha so it show same issue,
solution , add recaptcha solver within gsa cb , limit simultaneously captcha requests and lewer the cpu usage
Comments
solution , add recaptcha solver within gsa cb , limit simultaneously captcha requests and lewer the cpu usage