SQL-based search attributes not using proper attribute name on eager workflow start

[dhiaayachi]

Expected Behavior

Eager workflow start task should have the same search attributes as polling workflow task when starting a workflow with a custom search attribute.

Actual Behavior

Eager workflow start task has search attribute like Keyword03, whereas the polling workflow task has the proper attribute name.

Steps to Reproduce the Problem

1. Create a custom search attribute
2. Start a workflow with eager workflow start enabled and setting this search attribute
3. Confirm the resulting task in the start workflow gRPC response does not have the right key name for the search attribute

[dhiaayachi]

Thank you for reporting this issue. It appears that the eager workflow start task does not correctly set the custom search attribute when starting a workflow.

We are looking into this issue and will update the documentation once we have more information.

In the meantime, you can work around this issue by using the polling workflow task instead of the eager workflow start task.

Please provide the following information so we can investigate this further:

• What version of Temporal are you using?
• Can you share the code you are using to start the workflow?
• Can you provide the output of the start workflow gRPC response?

We appreciate your help in identifying and resolving this issue.

[dhiaayachi]

Thank you for reporting this issue. It seems like you've encountered a discrepancy between the search attribute names used in eager workflow start tasks and polling workflow tasks. We'll look into this issue to understand the root cause and address it in future releases.

In the meantime, you can use the Temporal UI or the Temporal CLI to search for workflows based on the actual search attribute name.

For example, if your custom search attribute is called "MyAttribute" and its value is "MyValue", you can use the following command to find the workflow using the Temporal CLI:

temporal workflow search --name "MyWorkflow" --query "MyAttribute:MyValue"

Let me know if you have any further questions or if you need additional assistance.

[dhiaayachi]

Thank you for reporting this issue.

It appears there's a discrepancy in how search attributes are handled between eager workflow start tasks and polling workflow tasks. We'll investigate this further.

In the meantime, you can work around this issue by retrieving the search attribute from the workflow start task using the WorkflowExecutionInfo returned in the StartWorkflowExecutionResponse. This response contains the searchAttributes field, which provides a map of the search attributes set for the workflow.

Please provide the following information to help us diagnose the issue further:

1. The version of Temporal you are using.
2. The code snippet for your workflow definition and how you're setting the custom search attribute.

We appreciate your patience and cooperation.

[dhiaayachi]

Thanks for reporting this issue. We'll investigate it further. It looks like you're encountering a discrepancy between search attribute names when starting a workflow eagerly vs. polling.

To help us better understand the issue, could you please provide:

• Temporal version: The Temporal Server version you are using.
• Workflow code: A snippet of the code where you are starting the workflow and setting the search attribute.

This information will be very helpful in diagnosing the cause of the problem and finding a solution.