Skip to content

Debug messages for failed answer #32

@petermr

Description

@petermr

The chatbot sometimes fails to give a useful answer and returns a stock phrase. We need to debug this. There are probably multiple causes and I guess at least:

servers

  • client server not running or timeout
  • backend not running or timeout (Cloudflare)
  • LLM-RAG not running or timeout
  • GROQ not running or timeout

resources

  • Cloudflare resource limit (time or number of accesses)
  • GROQ resource limit (time or number of accesses)
  • LLM RAG resource limit (time or number of accesses)

material/content

  • question cannot be answered by CABook

PLEASE TRY THE CHATBOT WITH SEVERAL QUESTIONS, AND GIVE AS MUCH BACKGROUND AS POSSIBLE

  • background - restarted server, refreshed screen, questions worked earlier, etc.

This is NOT EASY TO DEBUG.

@aleenaharoldpeter . Please include debug original messages as well as the human message ("could not find answer", etc.) We may be able to come up with a range of messages

@aleenaharoldpeter you may be able to delegate this task.

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions