Testing server continue-as-new doesn't carry search attributes

[jasonmchan]

Expected Behavior

When using ContinueAsNew with the testing server, the requested Search Attributes should be propagated into the new workflow execution.

This is what the production Temporal server does.

Actual Behavior

The search attributes in the command are dropped. See here for where the start request is constructed—the search attributes are not extracted from the ContinueAsNewWorkflowExecutionCommandAttributes.

Steps to Reproduce the Problem

1. Start a testing server
2. Run a workflow that uses continue-as-new with search attributes

Specifications

• Version: v1.31.0
• Platform: all

[baekgyu-kim]

Hello @Quinn-With-Two-Ns and @jasonmchan ,
I opened a PR that should address this issue.

When you have a chance, could you please take a look?
Thank you!

[maciejdudko]

Hi @jasonmchan and @baekgyu-kim,

After double-checking Temporal Server behavior, only Search Attributes are preserved on Continue-as-New, memos are not. I've edited the issue title and description accordingly.

[maciejdudko]

After further research, it turns out Search Attributes are not preserved by Temporal Server either. We have client-side logic in the SDK to automatically transfer SA when none are set in the request (SyncWorkflowContext.java), and this gives the illusion it's the server doing this work.

This means the current Test Server behavior matches the real Server and there's nothing that needs to be fixed here.