Hi folks, Trying to implement the following pattern with the help of signalWithStart. If a workflow with a given ID exists, signal will enqueue the next token to be processed for a given ID in a queue. Workflow method will pop it out in a loop and process. Workflow finishes when queue is empty. I…

Is the runId expected to stay the same across runs?

If I wait in between two executions to allow the first one to complete, then I get WorkflowExecutionAlreadyCompletedError for the second execution.

A gist of my workflow is as follows @SignalMethod fun enqueue(token: TokenType) { tokensToProcess.add(token) logger.info("Enqueued token" + token) } @WorkflowMethod fun process(workflowParam: WorkflowParamType) { while (tokensToProcess.isNotEmpty()) { val token = tokensToPro…

[image] mpnikhil: WorkflowExecutionAlreadyCompletedError Workflow is already completed: COMPLETED WorkflowExecutionAlreadyCompletedError(message:Workflow is already completed: COMPLETED) at app//com.uber.cadence.internal.testservice.TestWorkflowMutableStateImpl.checkCompleted(TestWorkflowMut…

[image] mpnikhil: The first token is indeed being processed twice because it was enqueued twice. Do you see two signals in the history?

Let me check. This is a test environment so I dont have a web UI to check the history. Any quick way to verify this?

Looks like in test env, all runIds will be the same. Could that be causing issues here? Any way to mitigate it if it is the case?

For this one even setting .setWorkflowIdReusePolicy(WorkflowIdReusePolicy.AllowDuplicate) does not help :frowning:

Ok I see only 2 signal events in the history HistoryEvent: eventType:WorkflowExecutionSignaled. Is the first signal being replayed somehow?

[image] Possible race condition between signalWithStart and continueAsNew? Community Support Temporal eliminates this race and forces the workflow to rewind and replay to include the last signal if it arrives while a workflow task is being processed where the code decides …

signalWithStart weird behaviour

Community Support

mpnikhil October 21, 2023, 12:58am 14

Could this be happening @maxim ? I am sending another signal while the workflow method is still processing the previous token. Does cadence replay all received signals so far?

Topic		Replies	Views
Continuously signalWithStart behaviour Community Support java-sdk	7	240	January 17, 2025
SignalWithStartWorkflow starting point Community Support go-sdk	13	2377	July 12, 2020
How does signalWithStart prevent race conditions with a DynamicWorkflow? Community Support java-sdk	6	1854	September 30, 2022
Awaiting workflow with signals - Null workflowId. Was workflow started? Community Support workflow-options	4	2310	March 13, 2024
How do Signals and workflow stored state interact? Community Support java-sdk , signals	9	2996	February 20, 2024

signalWithStart weird behaviour

Related topics