Skip to content

Add AI Transport SDK error codes (104000-104011)#343

Open
zknill wants to merge 2 commits into
mainfrom
zak/ait-720/channel-publish-user-message
Open

Add AI Transport SDK error codes (104000-104011)#343
zknill wants to merge 2 commits into
mainfrom
zak/ait-720/channel-publish-user-message

Conversation

@zknill

@zknill zknill commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Register the AI Transport SDK's 104xxx custom error codes so SDK
validation against this registry passes. The codes cover SDK-specific
scenarios that don't map cleanly to existing entries:

  • 104000-104008 — encoder recovery, transport lifecycle, channel
    continuity, stream piping (added with earlier branches).
  • 104010 "run start deadline exceeded" — client send() did not
    observe x-ably-run-start within the configured deadline.
  • 104011 "user prompt not found within lookup deadline" — agent's
    channel-rewind lookup for the client-published user message
    lapsed without a match.

Capability failures reuse Ably's existing 40160 ("operation not
permitted with provided capability") rather than coining a new code.

zknill added 2 commits May 15, 2026 15:01
Register the AI Transport SDK's 104xxx custom error codes so SDK
validation against this registry passes. The codes cover SDK-specific
scenarios that don't map cleanly to existing entries:

- 104000-104008 — encoder recovery, transport lifecycle, channel
  continuity, stream piping (added with earlier branches).
- 104010 "run start deadline exceeded" — client send() did not
  observe x-ably-run-start within the configured deadline.
- 104011 "user prompt not found within lookup deadline" — agent's
  channel-rewind lookup for the client-published user message
  lapsed without a match.

Capability failures reuse Ably's existing 40160 ("operation not
permitted with provided capability") rather than coining a new code.
Used by @ably/ai-transport when channel.history() pagination
exhausts its bounded retry budget during conversation hydration.
@lmars

lmars commented Jul 9, 2026

Copy link
Copy Markdown
Member

@zknill we recently updated how error codes are maintained in this repo, so if these new codes are still needed, they need to be registered by creating a Markdown file in the errors/codes directory.

Also worth noting that this looks to be a dupe of #331 (cc @mschristensen).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants