ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Responses API failing with read timeouts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Describe the bug
Since mid January, many calls (not all) to the Kaapi responses API (all with conversation ID) from Glific has failed with the error messages in the attached sheet.
To Reproduce
Steps to reproduce the behavior:
- Call the responses API with a conversation ID
Expected behavior
Successfully returns the response to the query
Additional context
Errors: https://docs.google.com/spreadsheets/d/1EdQ2A5tDyH51yRfe1wqst5P_DpqTUWkMKIPAKH9g3kk/edit?gid=2115979556#gid=2115979556
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a Responses API call with a conversation ID, then review the attached error spreadsheet for the read-timeout patterns. Trace the request through the backend and verify that these calls return successfully without read timeouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100