Circle V2 API Docs
    Preparing search index...

    Type Alias FormFillingDegradationKind

    FormFillingDegradationKind:
        | "no_vector_stores"
        | "no_documents_selected"
        | "no_retrieval_results"
        | "tool_error"
        | "field_timeout"
        | "field_error"
        | "dropped_citations"
        | "answered_without_retrieval"
        | "empty_answer_value"
        | "unanswered_sub_field"
        | "excess_list_values"
        | "uncited_answer"
        | "low_confidence"
        | "exclusivity_violation"
        | "evidence_budget_exceeded"
        | "answer_exceeds_box"
        | "answer_shortened_on_retry"

    A non-fatal problem worth surfacing on the run. v1 swallowed every one of these, so a run whose retrieval returned nothing looked exactly like a clean one in the database.

    Type Declaration

    • "no_vector_stores"
    • "no_documents_selected"
    • "no_retrieval_results"
    • "tool_error"
    • "field_timeout"
    • "field_error"
    • "dropped_citations"
    • "answered_without_retrieval"

      Answered without a chart tool call, so the field was re-asked; distinct from an honest no_retrieval_results blank.

    • "empty_answer_value"

      Reported answered but gave nothing the field's type could carry.

    • "unanswered_sub_field"

      A filled field with sub-fields that got no value. Counts only: naming them would disclose by complement what the chart said.

    • "excess_list_values"

      The list answer had more items than the field has boxes; the surplus was dropped.

    • "uncited_answer"
    • "low_confidence"
    • "exclusivity_violation"
    • "evidence_budget_exceeded"
    • "answer_exceeds_box"

      A filled text answer longer than its box holds; drawn in full, so the reviewer must see it.

    • "answer_shortened_on_retry"

      The first answer ran past the box; the re-ask's shorter answer replaced it.