Skip to content

fix: only set Nexus start on_conflict_options when there's something to attach - #1799

Open
tekkaya wants to merge 1 commit into
mainfrom
nexus-onconflict-linkless
Open

fix: only set Nexus start on_conflict_options when there's something to attach#1799
tekkaya wants to merge 1 commit into
mainfrom
nexus-onconflict-linkless

Conversation

@tekkaya

@tekkaya tekkaya commented Sep 1, 2026

Copy link
Copy Markdown

What was changed

on_conflict_options on Nexus-context workflow/activity starts is now only set when there are links or callbacks to attach, instead of unconditionally. Server rejects on_conflict_options when no links or callbacks exist to attach.

Why?

Matches sdk-go (and sdk-java's in-progress alignment, temporalio/sdk-java#3048) — the attach flags were previously always enabled even with nothing to attach.

Checklist

  1. Closes N/A, resolves a misalignment between other SDKs on on_conflict_options population in start activity request
  2. Tested: Ran tests/ locally.
  3. Docs: none — private functions only.

@tekkaya
tekkaya force-pushed the nexus-onconflict-linkless branch from 3fbf394 to 4abaa11 Compare September 1, 2026 00:25
…to attach

Matches sdk-go; the attach flags were previously always enabled even
with no links or callbacks to attach, which the server rejects.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@tekkaya
tekkaya force-pushed the nexus-onconflict-linkless branch from 4abaa11 to 54278a7 Compare September 1, 2026 00:26
@tekkaya
tekkaya marked this pull request as ready for review September 1, 2026 00:33
@tekkaya
tekkaya requested a review from a team as a code owner September 1, 2026 00:33
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