Class in Errors · JavaScript & TypeScript
A fresh gateway-count call could not return its complete result
A failure releases this call's local wait and request slot and withdraws its unsent commands without retrying or caching partial counts. It does not cancel provider work already dispatched or establish whether that work continued. Error metadata includes no credential, requested IDs, correlation nonce or provider body
class CountOperationError extends FluxerlyErrorclass CountOperationError
extends FluxerlyErrorConstructor#
Describe a count failure
Construction sends no request and releases no request slot
new CountOperationError(
options: {
readonly cause?: unknown
readonly inputValidation?: InputValidationDetail | null
readonly operation: CountOperation
readonly reason:
| "input" | "timeout" | "busy" | "response"
| "notConnected" | "connectionLost"
}
): CountOperationErrornew CountOperationError(
options: {
readonly cause?: unknown
readonly inputValidation?:
| InputValidationDetail
| null
readonly operation:
CountOperation
readonly reason:
| "input" | "timeout"
| "busy" | "response"
| "notConnected"
| "connectionLost"
}
): CountOperationErrorParameters
options-
causeoptional-
Underlying failure retained as the error's cause
unknown inputoptionalValidation -
Safe local input detail
It never retains rejected values, credentials, or Fluxer data, and names an unsupported key only when it looks like a field name. Defaults to null
InputValidationDetail | null operation-
Requested count operation
CountOperation reason-
Failure category, as described on the reason field
| "input" | "timeout" | "busy" | "response" | "notConnected" | "connectionLost"| "input" | "timeout" | "busy" | "response" | "notConnected" | "connectionLost"
Properties#
_tag#
Fixed name that identifies this error type
readonly _tag: "CountOperationError"inputValidation #
SDK-owned local input detail, or null for non-input failures
readonly inputValidation: InputValidationDetail | nullreadonly inputValidation:
| InputValidationDetail | nulloperation#
Requested count operation
readonly operation: CountOperationreason#
Failure category
The reason input means local validation failed, and not means a routed shard is absent or not ready. The reason busy means shared request capacity or a shard's internal command queue is full, and timeout means the reply deadline expired. The reason connection means a participating shard lost its connection, and response means a matched reply was malformed
readonly reason:
| "input" | "timeout" | "busy" | "response" | "notConnected"
| "connectionLost"readonly reason:
| "input" | "timeout" | "busy"
| "response" | "notConnected"
| "connectionLost"Inherited#
Inherited from Fluxerly: code, details, hint, to