@qtsurfer/api-client
    Preparing search index...

    Type Alias DatasetImportState

    Progress of one import, from fetching through ingest. fetching is the one status only an import ever reports — an upload's file already exists by the time you can poll it; an import's doesn't, until this source finishes fetching it.

    type DatasetImportState = {
        error?: string;
        importId: string;
        jobId?: string;
        status: "fetching" | "ingesting" | "ready" | "failed";
        version?: DatasetVersion;
    }
    Index
    error?: string

    A human-readable reason, present when status is failed — an unresolvable pool/pair, no data in the requested range, a range older than the configured source retains, the fetch exceeding your tier's time ceiling, or any of DatasetUploadState.error's own ingest-side reasons once fetching hands off to it. Durably recorded, same as on the upload path.

    importId: string
    jobId?: string

    The fetch/ingest job id, while status is fetching or ingesting.

    status: "fetching" | "ingesting" | "ready" | "failed"
    • fetching — reading from the source; nothing staged yet.
    • ingesting — fetch complete, staged, and re-entered the same ingest chain an upload uses; the worker is parsing and validating it.
    • ready — ingested successfully. version carries the result.
    • failed — the fetch or the ingest that followed it was rejected. error names why.
    version?: DatasetVersion

    Present when status is ready or failed.