Could not parse the regular response suddenly

Hi @cloudchan,

This error means your server is replying with something other than the expected data format, usually an error page or a PHP warning in front of the actual reply. Since it started right after a burst of content generations and now affects all your chatbots, my first suspect is a security or rate-limiting layer that got triggered by those repeated requests. Wordfence and similar security plugins, or your host’s firewall, often do this.

→ Open your site, then open browser DevTools (F12) and go to the Network tab. Send a message to the chatbot and click the failing request (it’s called “submit”). Then look at the Response tab.

What you see there tells us everything. An HTML page mentioning a firewall, security check, “rate limit,” or an error code like 503 means your security plugin or host is blocking the requests, so whitelist the /wp-json/mwai-ui/ path or wait for the throttle to lift. A PHP warning or fatal error means please copy it here, that’s the exact bug (a memory limit error is common after heavy generations, and your host can raise memory_limit). Nothing at all means the request timed out, usually a max_execution_time issue on long generations.