Execution of the LocalActivities happens asynchronously from the workflow execution. If the local activity has already been canceled by the time it goes to start the activity then the started listener is never invoked, and the test observes only a single activity being started. This is valid as the Workflow is written so adjust the assertion against it.
This seems to be happening more frequently after we migrated our CI, internal reference CDNC-9656
Execution of the LocalActivities happens asynchronously from the workflow execution. If the local activity has already been canceled by the time it goes to start the activity then the started listener is never invoked, and the test observes only a single activity being started. This is valid as the Workflow is written so adjust the assertion against it.
This seems to be happening more frequently after we migrated our CI, internal reference CDNC-9656
What changed?
Why?
How did you test it?
Potential risks