Skip to content

Add error code 92008 for apply-on-ACK abandonment of wait-for-SYNCED#328

Open
lawrence-forooghian wants to merge 1 commit intomainfrom
AIT-280-objects-sync-error-code
Open

Add error code 92008 for apply-on-ACK abandonment of wait-for-SYNCED#328
lawrence-forooghian wants to merge 1 commit intomainfrom
AIT-280-objects-sync-error-code

Conversation

@lawrence-forooghian
Copy link
Collaborator

This is the code that a LiveObjects mutation operation will fail with if the channel enters DETACHED, SUSPENDED, or FAILED whilst waiting for the objects sync state to become SYNCED. See ably/specification#419.

This is the code that a LiveObjects mutation operation will fail with if
the channel enters DETACHED, SUSPENDED, or FAILED whilst waiting for the
objects sync state to become SYNCED. See [1].

[1] ably/specification#419
lawrence-forooghian added a commit to ably/specification that referenced this pull request Feb 16, 2026
…20e1)

The RTO20e wait for the objects sync to reach SYNCED has no failure
condition, which means publishAndApply can hang indefinitely if the
channel never completes the sync — for example, during a disconnection
loop where publish succeeds (ACK received) but the OBJECT_SYNC sequence
never finishes.

This adds RTO20e1 to fail the operation when the channel enters DETACHED,
SUSPENDED, or FAILED. The objects sync requires the channel to be
ATTACHED to receive the OBJECT_SYNC sequence (RTO4c), so waiting for
sync is essentially waiting for the channel to become attached. The
decision of when to give up on that is already established by RTL11:
queued presence messages — which are also waiting for the channel to
become ATTACHED (RTP16b) — are failed when the channel enters DETACHED,
SUSPENDED, or FAILED. We apply the same rule here.

The error uses code 92008, in the objects error range in ably-common.
Added in [1].

[1] ably/ably-common#328

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@VeskeR
Copy link

VeskeR commented Feb 18, 2026

@lawrence-forooghian
Copy link
Collaborator Author

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

Comments