GapFillFailureReason

Why one splice-fill did not complete. Each arm names a different owner (this SDK’s own composition, the transport, the host), because the repair differs:

• noConnection — the Session was built fold-only, so it has no seam to page through. Composition, not a runtime fault.
• pageFailed — a view/page round trip failed, or answered with a frame this session may not fold. cause carries it.
• pageStalled — the walk made no progress: a page that neither carried events nor ended the view, or a nextCursor that did not advance. The wire is an external boundary and this is the only bound on the walk; an attempt cap would silently truncate a legitimate long fill.

Source

clients/sdk-ts/src/errors.ts:45

{
  "kind": "Type alias",
  "canonicalPath": "GapFillFailureReason"
}