-
Bug
-
Resolution: Fixed
-
Major
-
1.0.2
-
None
Currently all activation threads share same instance of activation content. This can lead to issues when different subscribers try to activate content in different parent path if they are executed in very short time window apart (the paths get mixed). The solution to the issue is to ensure each of the activation threads uses its own copy of the ActivationContent.
Acceptance criteria
- depends upon
-
MAGNOLIA-2807 Make ActivationContent clonable
- Closed