Skip to content

Commit 5139dda

Browse files
docs(connect): qualify held webhook order and best-effort clears
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent 92419bf commit 5139dda

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

‎docs/internals/t3-connect.md‎

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,16 @@ raw request, including the hook token in the path, in a Durable Object with
1818
SQLite storage. There is one object per managed link, keyed by its endpoint
1919
key: each account that links the environment gets its own held requests,
2020
order, and caps. The object pushes held requests back through the tunnel from
21-
its alarm, oldest first, and backs off while the environment stays away. When
21+
its alarm, oldest first within each hook, and backs off while the environment
22+
stays away. A hook that answers busy is skipped for the rest of that run, so
23+
other hooks on the link can overtake it. When
2224
the tunnel reconnects, the environment asks the relay to deliver right away to
2325
each of its links. Requests are deleted once the environment answers, after 24
2426
hours, when their link is unlinked, or when the environment turns holding off,
25-
which clears every link it proved. The relay still never checks the token;
27+
which clears every link it proved. Both clears are best effort: unlinking logs a
28+
failed clear and continues, and turning holding off stops at the first link it
29+
cannot clear, so those requests wait for the 24-hour expiry. The relay still
30+
never checks the token;
2631
delivery goes through the same environment route.
2732
Every forward carries `x-t3-relay-delivery-id`, so a request that reached the
2833
environment before a timeout and is delivered again later runs once

0 commit comments

Comments
 (0)