4 ms·
Tested out the landing page chatbot and got one “We couldnt find an answer to your question” and another request timeout. Not confident at all using this with a
by pech0rin 3y ago
Tested out the landing page chatbot and got one “We couldnt find an answer to your question” and another request timeout. Not confident at all using this with any product.
- dazzeloid 3y agoOops looking into it. Do you remember which bot you used and what question you asked?
- AugurCognito 3y agoSame issue here, toggled ai chats only and selected one of the default questions, maybe api met hn hug of death(?)
- dazzeloid 3y agoWahhh. Strava example?
- AugurCognito 3y agoAfter some digging I discovered something. This error happens when occurrence API returns 400 Bad Request error. This led me to identify two scenarios in which it can happen: 1. When a query is sent while another query is being processed, it consistently triggers a 400 bad request error. Subsequent queries also yield the same error code. 2. Although less common, random queries can sometimes result in a Bad Request error. I do not know how helpful this information is, but I can provide the chat_id associated with the instance: 677cfad3-5084-40d0-81d0-08592b5927f5.
- vayyala 3y agoGreat catch - should be fixed now!
- melvinmelih 3y agoWell, what do you expect from a product that is put together as a AI-related side quest :)
- dazzeloid 3y agoit's a main quest now!!