90 symbols from @neontechspace/fluxerly/effect
Re-Exports#
Declared in JavaScript & TypeScript and documented there. Import them from @neontechspace/fluxerly/effect as well
describe#Error - Describe any error as readable multi-line text: Its name, SDK code, message, suggested fix, safe details and cause chain
errors#- Error helpers that classify and match errors through
api,Code is,Not Found is,Retryable retry, outcome and matchAfter Ms Application#Error - An application callback invoked by the SDK failed, threw or rejected
Asset#Url Error - The SDK could not make an asset URL from the supplied input
Attachment#Download Error - Expected bounded attachment-download failure, without a URL, response body or credential
Attachment#Refresh Error - The SDK could not refresh one ordered batch of attachment URL strings
Authentication#Error - Fluxer rejected the bot token during connection startup or recovery
Bot#Application Operation Error - The SDK could not read the current bot application
Channel#Operation Error - Expected failure when reading or changing community channels, threads and forum tags
Client#Busy Error - A competing connection operation already owns the client, so this call did not take ownership
Client#Closed Error - The client is permanently closing or closed, so reconnecting requires a new client
Collector#Error - Expected collector failure, separate from results that stop at the count, deadline, idle deadline or explicit stop
Configuration#Error - A client setting or operation option is invalid before the requested work starts
Connection#Error - Instance discovery or the gateway connection failed
Connection#Timeout Error - Gateway startup or explicit instance discovery exceeded its time budget
Count#Operation Error - A fresh gateway-count call could not return its complete result
Critical#Worker Stopped Error - One of the bot's event or command subscriptions ended while its client was still running
Event#Overflow Error - An event subscription stopped because unread events exceeded its count or byte limit
Event#Read Busy Error - A second next call tried to read while the same default API pull subscription already had a pending read
Event#Wait Error - A filtered event wait ended without a match or could not use its synchronous filter
Fluxerly#Error - Base class for every error the SDK returns, throws or reports, in both entry points
Gateway#Send Error - Why
gatewaydid not hand a command to the shard's connection.send Guild#Operation Error - Expected failure from guild, member, role and related resource operations
Helper#Error - A helper could not use its input
Member#Chunk Error - A member stream stopped before it could return every batch
Message#Cleanup Error - A cleanup preview or deletion failed, with selected IDs and batch progress where available
Message#Error - A send, reply or forward ended without confirming that Fluxer created the message
Message#Operation Error - A message lookup, read or change failed
OAuth#Operation Error - An OAuth call failed an input check, reached a local capacity limit, or failed during its request or response
Pagination#Error - Reading multiple pages failed because of invalid settings, a page limit, a stalled cursor or search readiness
Presence#Error - The SDK rejected a status update or member-presence selection before changing its saved settings
Rate#Limit Error - Discovery HTTP or the gateway imposed a connection rate limit
Rest#Request Error - Expected failure of
client.rest .request Shard#Connection Error - A configured gateway shard failed startup or permanently lost its established connection
Supervisor#Child Error - Child-helper failure because the parent's message channel is unavailable or carries invalid coordination data
Supervisor#Error - Parent-process lifecycle failure, not the child's original client or configuration error
User#Operation Error - Expected failure from account reads or private-conversation operations
Webhook#Operation Error - An expected failure while managing a webhook or one of its messages
Api#Error Detail - Safe details about a Fluxer API rejection, available in an operation error's
apifieldError Api#Validation Error Detail - A validation error reported by Fluxer, with a fixed SDK explanation
Describe#Error Options - Settings for
describeError Error#Tools - Helpers for inspecting SDK errors in either entry point
Fluxerly#Error Json - The JSON form of an SDK error, produced by
toJSON Fluxerly#Error Options - Settings shared by SDK error constructors
Input#Validation Detail - Describes why the SDK rejected an input without keeping the rejected value
Message#Cleanup Failure Metadata - Expected batch failure details included in a failed progress notification
Operation#Error Options - Constructor settings shared by resource operation errors, such as
GuildandOperation Error MessageOperation Error Api#Error Code - Stable SDK category of a recognized Fluxer API rejection, read from
ApiError Detail .code Api#Provider Code - Exact Fluxer server code that the SDK recognizes, read from
ApiError Detail .provider Code Api#Validation Code - Exact Fluxer validation code that the SDK recognizes, read from
ApiValidation Error Detail .provider Code Attachment#Download Failure - Expected attachment-download failures shared by both entry points
Attachment#Refresh Failure - Expected attachment URL refresh failures shared by both entry points
Attachment#Refresh Operation - Attachment URL refresh operation identified by safe failure metadata
Bot#Application Operation - Operation name included in application-read failures
Bot#Application Operation Failure - Expected application-read failures in both APIs
Channel#Operation - The channel or thread action named in an expected failure or
SdkDefect Channel#Operation Failure - Native interruption is outside this union, with default API methods additionally returning
CancelledError Collector#Failure - Expected terminal failures shared by both API styles
Connect#Error - Expected connect and run failures, with default API methods adding
Cancelledto their result unionError Connection#Failure - Expected startup or terminal connection failures, excluding cancellation and SDK defects
Count#Operation - The guild or channel count request named in an error
Count#Operation Failure - Expected fresh-count failure
Error#Match Handlers - Handlers for
errors, keyed by each possible error's _tag, plus an optional _ fallback.match Event#Read Error - Expected subscription-read failures from queue overflow or a competing pending read
Event#Wait Failure - Expected filtered event-wait failures, including invalid options, client closure, queue overflow, deadline expiry or a failed filter
Gateway#Send Failure - Expected
gatewayfailures in both APIs.send Guild#Operation - The guild or related-resource action named in an expected failure or
SdkDefect Guild#Operation Failure - Native interruption is outside this union
Input#Validation Constraint - Identifies why the SDK rejected an input before sending a request
Instance#Resolve Error - Expected instance-resolution failures, including invalid options, connection trouble, deadline expiry, rate limits and client closure
Member#Chunk Failure - Expected stream failure
Message#Cleanup Error Reason - Expected preview or cleanup failure classification
Message#Cleanup Failure - Expected preview and cleanup errors shared by both entry points
Message#Operation Failure - Message lookup, management and reaction failures shared by both entry points
Not#Found Resource - Resources that Fluxer reports as missing, accepted by
errors.is Not Found OAuth#Operation - Public OAuth call identified by operation-error metadata
OAuth#Operation Failure - Expected OAuth failures shared by both entry points
Operation#- Identifies the default API call during which an
Sdkwas observedDefect Operation#Outcome - Whether a request may have reached Fluxer
Operation#Reason - Why a remote operation failed
Paginate#Failure - Expected reaction page failures: Invalid pages or options, a failed send, a failed page change, arrow or click removal, an unavailable or lost gateway, an overflowing listener or a failing users check
Pagination#Operation - Operation name included in a
Paginationor default-API SDK defect to identify the traversalError Presence#Failure - Expected presence-operation failure
Rest#Operation - Operation name included in REST request failures
Rest#Request Failure - Expected REST request failures in both APIs
Send#Error - Expected message-creation failures shared by both entry points, including permanent client closure
User#Operation - User/private-conversation operation named by safe failure metadata
User#Operation Failure - Cancellation in the default API additionally returns
CancelledError Webhook#Operation - Identifies the webhook action that failed, so an error can be associated with the request the application made
Webhook#Operation Failure - Expected failures shared by webhook operations, including requests made after the client closes