Adobe Orchestrated Campaign: Native In-Flight Profile Status to Prevent Re-Entry Description

Introduce a runtime profile status to natively block profile re-entry while a user is still actively in-flight within an Orchestrated Campaign.

Why is this feature important to you For daily recurring campaigns, architects currently face overlapping, concurrent journeys because profiles are pulled in again before exiting the workflow. Resolving this currently requires maintaining a custom active flag explicitly in the data model and updating it via external systems, which adds unnecessary architectural overhead.

How would you like the feature to work OCM should natively expose a runtime profile status (such as "active" or "in-progress") that acts as a built-in mechanism to natively block campaign re-entry while a user is still actively in-flight.

Current Behaviour Unlike standard Journeys, OCM does not natively expose a runtime profile status, providing no built-in mechanism to natively block re-entry while a user is still in-flight