Member Junction
    Preparing search index...
    WebSearchResultCode:
        | "SUCCESS"
        | "MISSING_QUERY"
        | "NO_PROVIDERS_CONFIGURED"
        | "PROVIDER_LOAD_FAILED"
        | "NO_ELIGIBLE_PROVIDER"
        | "PROVIDER_NOT_FOUND"
        | "PROVIDER_NOT_ACTIVE"
        | "PROVIDER_UNAVAILABLE"
        | "PROVIDER_LACKS_CAPABILITY"
        | "ALL_PROVIDERS_FAILED"
        | "INVALID_REQUEST"

    Outcome codes. SUCCESS is the only one where WebSearchResult.Success is true.

    Type Declaration

    • "SUCCESS"
    • "MISSING_QUERY"

      Query was missing or blank.

    • "NO_PROVIDERS_CONFIGURED"

      No web search providers exist in metadata at all — a setup problem, not a search failure.

    • "PROVIDER_LOAD_FAILED"

      The provider list could not be READ — the view query failed, the entity is absent from metadata, or the caller lacks permission. Deliberately distinct from NO_PROVIDERS_CONFIGURED: that one tells an operator to add a record, which is the wrong instruction (and an actively misleading one) when the read itself never succeeded.

    • "NO_ELIGIBLE_PROVIDER"

      Providers exist, but none is Active, available and capable of this request.

    • "PROVIDER_NOT_FOUND"

      An explicit Provider was named and no such provider exists in metadata.

    • "PROVIDER_NOT_ACTIVE"

      The named provider exists but its Status is not Active.

    • "PROVIDER_UNAVAILABLE"

      The named provider is Active but not operational — usually a missing credential.

    • "PROVIDER_LACKS_CAPABILITY"

      The named provider cannot do what was asked, e.g. IncludeAnswer on a hits-only provider.

    • "ALL_PROVIDERS_FAILED"

      Every eligible provider was tried and each failed. See Attempts.

    • "INVALID_REQUEST"

      The request itself was rejected and retrying elsewhere cannot help.