langflow-ai/langflow · error · HTTPException

Access denied: knowledge base '{kb_name}' is managed by a Me

Error message

Access denied: knowledge base '{kb_name}' is managed by a Memory Base.

What it means

Error "Access denied: knowledge base '{kb_name}' is managed by a Memory Base." thrown in langflow-ai/langflow.

Source

Thrown at src/backend/base/langflow/api/v1/knowledge_bases.py:316

    resolved owner via :func:`_assert_kb_not_memory_base` so a shared
    Memory-Base-managed KB still gets blocked.

    A missing local directory is NOT treated as a 404 here because the
    delete route handles the orphan-DB-row case downstream. This dep
    only blocks Memory-Base-managed KBs from being touched; an
    orphan row can't have Memory-Base metadata because that metadata
    lives in the on-disk ``embedding_metadata.json`` which is gone.
    """
    try:
        kb_path = _resolve_kb_path(kb_name, current_user)
    except HTTPException as exc:
        if exc.status_code == HTTPStatus.NOT_FOUND:
            return  # Let the route body handle the missing-dir case.
        raise

    metadata = KBAnalysisHelper.get_metadata(kb_path, fast=True)
    if _is_memory_base_associated(metadata):
        raise HTTPException(
            status_code=403,
            detail=f"Access denied: knowledge base '{kb_name}' is managed by a Memory Base.",
        )


def _assert_kb_not_memory_base(kb_name: str, owner_user) -> None:
    """Post-resolution memory-base check.

    The FastAPI dep :func:`_check_memory_base_association` only sees the
    actor; for cross-user-reached KBs (a non-owner with a share grant) it
    short-circuits because the actor has no same-named local KB. Route
    bodies call this helper after :func:`_guard_kb_action` resolves the
    real owner so Memory-Base-managed KBs are still blocked even when
    reached through a share.
    """
    try:
        kb_path = _resolve_kb_path(kb_name, owner_user)
    except HTTPException as exc:

View on GitHub (pinned to 976ec789d2)

Solutions

1. Manage this knowledge base through its owning Memory Base instead of the KB API.

When it happens

Trigger: Occurs when attempting to directly modify a knowledge base that is managed by a Memory Base and therefore read-only via this API.

Common situations: See trigger scenarios.

Understand the failure class

• Authentication and authorization failures — expired tokens, bad credentials, and missing scopes.

AI-assisted analysis of langflow-ai/langflow@976ec789d2 (2026-08-14). Data as JSON: /api/errors/1f016aad8a56e5ce. Report an issue: GitHub.