Skip to content

"No object generated: couldn't parse the response" #110

@Alejkaw

Description

@Alejkaw

I was testing a complex prompt that requested multiple pieces of information. It took a while, but then it suddenly stopped and showed the message: "No object generated: couldn't parse the response."

It seems this might be due to the length. Is there any workaround for situations where prompts or responses are too long?

The prompt was written in spanish:
“¿Podrías proporcionar los box scores detallados de los últimos 3 partidos jugados entre los Denver Nuggets y los Oklahoma City Thunder en los playoffs de la NBA de mayo de 2025? Para cada partido, necesito las estadísticas completas de AMBOS equipos, incluyendo como mínimo: Puntos (PTS), Tiros de Campo Anotados (FGM), Tiros de Campo Intentados (FGA), Triples Anotados (3PM), Triples Intentados (3PA), Tiros Libres Anotados (FTM), Tiros Libres Intentados (FTA), Rebotes Ofensivos (ORB), Rebotes Defensivos (DRB), Asistencias (AST), Robos (STL), Tapones (BLK), Pérdidas de Balón (TOV) y Faltas Personales (PF).”

Response:
"Thoughts
No object generated: could not parse the response."

Then, I tried trimming the prompt to only ask for PTS and FGM. It worked and returned a full, detailed response.

The issue is that when using prompts like these, there's no way to know in advance whether an error will occur (when using the API), which can result in wasted token usage with no useful output.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions