Skip to content

Conversation

@c-warren
Copy link
Contributor

@c-warren c-warren commented Sep 22, 2025

What changed?

Tests conflict resolution when the same workflowID is used to create workflows in two different clusters with an Active-Active setup in the domain.

Why?

Cadence does not support two workflows existing with the same workflow ID. When a domain is configured active-active it can be possible for a user to make two simultaneous requests to two different clusters with the same workflow ID. When this happens, both workflows will run temporarily until the clusters have replicated their data to the other, at which point the conflict will have to be resolved.

This test is a follow up to #7265, testing the scenario when SignalWithStart is used (rather than StartWorkflow).

How did you test it?

Locally + against dev canary domains.

Potential risks

N/A

Release notes

N/A

Documentation Changes

N/A

…the query_workflow step to correctly retrieve signals, cleaning up some of the configuration
Copy link
Member

@Shaddoll Shaddoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

# This file is a replication simulation scenario spec.
# It is parsed into ReplicationSimulationConfig struct.
# Replication simulation for this file can be run via ./simulation/replication/run.sh activeactive_same_wfid_signalwithstart_delayed
# Dynamic config overrides can be set via config/dynamicconfig/replication_simulation_activeactive_same_wfid_signalwithstart_delayed.yml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this dynamic config file is not created

@c-warren c-warren enabled auto-merge (squash) September 24, 2025 15:59
@c-warren c-warren merged commit 2050121 into cadence-workflow:master Sep 24, 2025
39 of 40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants