Skip to content

Fix: Persist unique key on auth failure - #837

Draft
dzikowski wants to merge 4 commits into
mainfrom
fix/persist-unique-key-on-auth-failure
Draft

dzikowski wants to merge 4 commits into
mainfrom
fix/persist-unique-key-on-auth-failure

Conversation

@dzikowski

Copy link
Copy Markdown
Collaborator

No description provided.

dzikowski and others added 3 commits September 17, 2026 12:24
Consume uniqueKey before authenticate so a failed submit still spends the key.

Co-authored-by: Cursor <cursoragent@cursor.com>
uniqueKey is global and the method is not in the signed payload, so spend
it from the raw submit even when this endpoint rejects the DTO.

Co-authored-by: Cursor <cursoragent@cursor.com>
Keep uniqueKey from the parsed DTO on the happy path. On throw, use that
value or read it from the raw submit so a rejected endpoint still spends it.

Co-authored-by: Cursor <cursoragent@cursor.com>
@dzikowski
dzikowski marked this pull request as draft September 17, 2026 14:54
Skip the catch persist when the error is already a uniqueKey conflict,
and keep that write in a helper.

Co-authored-by: Cursor <cursoragent@cursor.com>

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant