temporalio / temporalio/features
Add resource ID to the http header for API requests
@tconley1428 is already working on this.
Since Jul 6, 2026.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
Include workflowId in the header will enable the api gateway/frontend route the workflow request to correct active cluster without having to decode/open the request payload
Describe the solution you'd like
Workflow requests are requests for a specific workflow, i.e. StartWorkflow, RespondWorkflow/Activity, SignalWorkflow etc.
For actions initiated from the SDK (e.g., StartWorkflow, SignalWorkflow, TerminateWorkflow), the SDK needs to add the workflowId to the request header.
For action-after-poll requests (i.e., RespondWorkflow/ActivityTask), SDK only needs to attach the header from the matching poll response to the following API calls.
Additional context
server will add header at the poll response
Per-SDK Tickets
- Go -
- Java -
- Core -
- TypeScript -
- Python -
- .NET -
- Ruby -
- PHP -
- Temporal CLI -
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.