Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User-defined RequestId for SignalWorkflow #1705

Open
ndtretyak opened this issue Nov 7, 2024 · 1 comment
Open

User-defined RequestId for SignalWorkflow #1705

ndtretyak opened this issue Nov 7, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@ndtretyak
Copy link
Contributor

Is your feature request related to a problem? Please describe.
I want to use server-side deduplication for signals. However, RequestId is always set to uuid.New

RequestId: uuid.New(),

Describe the solution you'd like
An option to override the RequestId in each method, allowing users to specify their own identifier instead of a generated UUID.

@ndtretyak ndtretyak added the enhancement New feature or request label Nov 7, 2024
@Quinn-With-Two-Ns
Copy link
Contributor

Long term server side deduplication of signals by RequestId is not a stable feature users should rely on temporalio/temporal#4021 so it is intentionally not exposed in any SDK. If you want deduplication of signals the best approach is to put your own ID in the signal input and deduplicate in the workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants