Details:
Journeys that are already in progress at the time of a new deployment will not automatically adopt updated policies, journey models, or configuration changes. This behavior is based on point-in-time configuration referencing, which ensures that:
Once a journey is launched, it locks in the configuration, policies, and journey model version that were active at the time of initiation.
Any subsequent deployments (e.g., new policies, updated journey structures, or rulesets) will only apply to journeys triggered after the deployment.
This design ensures:
Stability in ongoing processes
Prevention of mid-journey inconsistencies
Avoidance of compliance risks due to unexpected behavior changes
Important Note:
To apply the latest configurations to entities already in a journey, the existing journey must be:
Closed (if permissible from a process/compliance standpoint)
Relaunched after the new deployment
Only then will the latest policies and logic be applied to those cases.