Repository navigation
docs(turbosign): drop NotSignersTurn, the API only returns RecipientNotInTurn - #217
Merged
Merged
Conversation
Contributor
Author
|
Self-review (author). No blocking issues found. Checked:
Notes for reviewers, no change requested:
|
amitsharma-turbodocx
force-pushed
the
fix/213-remove-not-signers-turn
branch
from
October 21, 2026 09:10
03c3b54 to
c64e5a5
Compare
…otInTurn (#213) The embedded-signing pages listed a 409 NotSignersTurn that createSigningUrl never returns: the only turn refusal is RecipientNotInTurn. Remove it from the error tables and prose, and retry only RecipientNotInTurn in the six code samples. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…odes too (#213) The API never returns NotSignersTurn; its only turn refusal is RecipientNotInTurn. This was the last mention left in the docs. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
amitsharma-turbodocx
force-pushed
the
fix/213-remove-not-signers-turn
branch
from
October 21, 2026 09:25
c64e5a5 to
869a440
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #213
Why
The embedded signing docs said
createSigningUrlcan return HTTP 409NotSignersTurn. The API never sends it. Its only turn refusal isRecipientNotInTurn. Nothing in the API ever raisesNotSignersTurn.What
build/sequential-signers.md: Step 3 prose, the retry code in all six language tabs (theTURN_RACEsets are now a singleRecipientNotInTurncomparison), and the Common errors row.index.mdandreference.md(2 tables): dropNotSignersTurnfrom the 409 rows.NotSignersTurnon purpose for cross-SDK parity.Verified
Against a local TurboDocx API and the built site:
409 ConflictErrorwith codeRecipientNotInTurn.mintNext, run verbatim against that API:RecipientNotInTurn.RecipientNotFoundat once, with no retries.py_compile,php -l,gofmt -e,java-parser,ruby -c).NotSignersTurnin the HTML of any of the three pages.?language=pythonstill selects the Python tab.docusaurus buildpasses. The 8 broken-anchor warnings are pre-existing (/docs/SDKs/*#error-handling) and identical on a branch that doesn't touch these pages.🤖 Generated with Claude Code
Update (2026-10-21): rebased on current
develop(after #219), and added869a440, which also dropsNotSignersTurnfrom the 409 row of Error Codes for Sending and Updating Recipients inAPI-Signatures.md. That was the last mention in the docs, sogit grep NotSignersTurn -- docsnow returns nothing. #216 (the earlier draft of this fix, againstmain) is closed as superseded.