Twill Brain

#301 [Bug]: there is no reason in "Failed to handle LLM Engine response in LLM" log when issue caused by ASGI

1 min read

#301 — [Bug]: there is no reason in “Failed to handle LLM Engine response in LLM” log when issue caused by ASGI

Repo: Twill-AI/facade State: closed | Status: done Assignee: Unassigned

Created: 2025-03-12 · Updated: 2025-09-15

Description

Steps to reproduce

Caused by https://twill-network.slack.com/archives/C07TPN6FCBX/p1741789228197559

Expected behavior

“Failed to handle LLM Engine response in LLM” logs always have a reason in the same line.

Actual behavior

2025-03-12 14:18:13.662|ERROR|lcltnnt7mf|websockets_router:506|4769c8d0-bdd6-4699-9b42-34cfc51afba2: Failed to handle LLM Engine response in LLM Chat 10. Reason:

log, so alerter can’t have “skip” rules to omit specific errors.

Investigation details

There is no artificial line feed (aka “\n”) in the error. It looks like error message is empty (in stack trace it is raise WebSocketDisconnect(code=1006)). So changed to log full error class name if there is no error message.

Notes

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets

Graph View