bytedance/deer-flow · error · HTTPException

Failed to get thread history

Error message

Failed to get thread history

What it means

Error "Failed to get thread history" thrown in bytedance/deer-flow.

Source

Thrown at backend/app/gateway/routers/threads.py:1493

            # Keep step for ordering context
            if "step" in metadata:
                user_meta["step"] = metadata["step"]

            entries.append(
                HistoryEntry(
                    checkpoint_id=checkpoint_id,
                    parent_checkpoint_id=parent_id,
                    metadata=user_meta,
                    values=values,
                    created_at=coerce_iso(snapshot.created_at or metadata.get("created_at", "")),
                    next=next_tasks,
                )
            )
    except _CHECKPOINT_MODE_ERRORS as exc:
        raise _checkpoint_mode_http_error(exc, thread_id) from exc
    except Exception:
        logger.exception("Failed to get history for thread %s", sanitize_log_param(thread_id))
        raise HTTPException(status_code=500, detail="Failed to get thread history")

    return entries

View on GitHub (pinned to 1dd6ba1acb)

Solutions

1. Check the Gateway logs for the underlying history read error.
2. Verify the thread exists and checkpoint storage is healthy, then retry.

When it happens

Trigger: Thrown at backend/app/gateway/routers/threads.py:1493 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of bytedance/deer-flow@1dd6ba1acb (2026-08-14). Data as JSON: /api/errors/56ca1b4ffb65513e. Report an issue: GitHub.