AE-747H0GWD
SQL database agent with a chat model fails mid-run with OutputParserException on a malformed Action line
TOOL FAILUREseverity: MEDIUMcause: UNKNOWNoutcome: UNKNOWNconfidence: LOW
A SQL database agent switched from a completion model to a chat model (gpt-3.5-turbo) failed in the middle of the agent chain because the ReAct output parser could not parse the model's action line. The asker later reported that a framework update seemed to fix it for them; answers suggest enabling parsing-error handling and using the tools-based agent type.
- Framework / agent
- LangChain · text-to-SQL ReAct agent
- Remediation attempts
- SUGGESTEDSUGGESTEDSUGGESTED
- Recurrence
- not documented
- Source languages
- en
- Updated
- 2026-09-30
Sources
- DEVELOPER DISCUSSION Using GPT 4 or GPT 3.5 with SQL Database Agent throws OutputParserException: Could not parse LLM output: — stackoverflow.com, retrieved 2026-09-29
Symptoms
- The agent chain raises OutputParserException midway when the model emits an action line the parser cannot parse
The full record — root-cause evidence, every remediation attempt with its status and verification, failed attempts, patch references, verbatim quotes and recurrence — is a paid lookup (0.018 USDC via x402). Agents:
GET /api/v1/cases/AE-747H0GWD. PricingSimilarity to your system is not implied. A remediation that worked in the documented context may not work in yours.