iflytek/astron-agent · error · Exception

Unable to ensure dataset exists

Error message

Unable to ensure dataset exists: {str(e)}

What it means

ensure_dataset's outer exception handler wraps any failure in the lookup/create sequence (network errors, RAGFlow client exceptions) with 'Unable to ensure dataset exists: ...'. It means the code could not guarantee a dataset exists, so the caller should abort ingestion for that group.

Solutions

1. Read the wrapped cause (str(e)) for the underlying failure
2. Check RAGFlow connectivity, credentials and dataset listing API
3. Implement retry with backoff for transient RAGFlow outages

When it happens

Trigger: Thrown at core/knowledge/infra/ragflow/ragflow_utils.py:140 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of iflytek/astron-agent@5e758547a8 (2026-09-12). Data as JSON: /api/errors/3b2998428cc1a36a. Report an issue: GitHub.

Appendix: source

Thrown at core/knowledge/infra/ragflow/ragflow_utils.py:140

                create_response = await create_dataset(
                    name=group,
                    description=description
                    or f"Automatically created dataset: {group}",
                    chunk_method="naive",
                )

                if create_response.get("code") == 0:
                    dataset_id = create_response.get("data", {}).get("id")
                    logger.info(
                        f"Dataset created successfully: {group}, ID: {dataset_id}"
                    )
                    return dataset_id
                else:
                    raise Exception(f"Dataset creation failed: {create_response}")

            except Exception as e:
                logger.error(f"Dataset management failed: {e}")
                raise Exception(f"Unable to ensure dataset exists: {str(e)}")

    @staticmethod
    async def _sync_description_if_stale(
        dataset_id: str, current: Optional[str], desired: Optional[str]
    ) -> None:
        """Best-effort lazy sync of a dataset's description.

        Skips when ``desired`` is empty (caller did not supply a label) or
        when ``current`` already matches. Exceptions are swallowed and logged
        — a UI-friendly description must never block document writes.
        """
        if not desired or current == desired:
            return
        try:
            resp = await update_dataset(dataset_id, description=desired)
            if resp.get("code") != 0:
                logger.warning(
                    "Best-effort description sync rejected by RAGFlow for "

View on GitHub (pinned to 5e758547a8)