zylon-ai/private-gpt · error · HTTPException

Async deletion is not supported by the configured scheduler

Error message

Async deletion is not supported by the configured scheduler

What it means

Error "Async deletion is not supported by the configured scheduler" thrown in zylon-ai/private-gpt.

Source

Thrown at private_gpt/server/ingest/ingest_router.py:967

def delete_ingested_async(
    request: Request, body: DeleteIngestedDocumentAsyncBody
) -> Task:
    """Initiates asynchronous deletion of a document and all associated data.

    This endpoint queues a deletion task for background processing, making it
    suitable for large documents or when non-blocking operation is required.
    The task can be monitored using the returned task ID.

    If an ingestion task is currently running for the same document, it will
    be automatically revoked before initiating the deletion.
    """
    scheduler = request.state.injector.get(IngestionSchedulerFactory).get()
    try:
        task_id = scheduler.delete_async(body)
    except NotImplementedError as exc:
        from fastapi import HTTPException

        raise HTTPException(
            status_code=501,
            detail="Async deletion is not supported by the configured scheduler",
        ) from exc
    return Task(task_id=task_id)


if _CELERY_AVAILABLE:

    @ingest_router.get(
        "/delete/async/{task_id}",
        response_model=TaskStatus[None],
        tags=["Artifacts"],
        summary="Check Deletion Task Status",
        description="Retrieve the current status of an asynchronous deletion task",
        responses={
            200: {
                "description": "Successfully retrieved task status",
                "content": {

View on GitHub (pinned to 4a030776a3)

Solutions

1. Configure a scheduler that supports async deletion (e.g. scheduler.chat.mode='arq' with the arq worker running).
2. Use the synchronous deletion endpoint instead of async deletion.
3. Enable the Redis/arq backend so the configured scheduler can process async deletion tasks.

When it happens

Trigger: Raised when an async deletion request is made but the configured scheduler cannot run deletion jobs asynchronously.

Common situations: Requesting async deletion of ingested documents with the local scheduler configured; use sync deletion or configure an async-capable scheduler.

AI-assisted analysis of zylon-ai/private-gpt@4a030776a3 (2026-08-15). Data as JSON: /api/errors/0fd9974732f4ebe7. Report an issue: GitHub.