ComposableStack.AI CDP
Back to agent
Constraintconstraint.aep-adhoc-concurrent-job-per-audience-1

AEP Ad-Hoc Activation — Maximum 1 Concurrent Job Per Audience (System-Enforced)

Adobe Experience Platform enforces a system limit of 1 concurrent ad-hoc activation job per audience. If an ad-hoc export job is already running for a given audience, a second ad-hoc job for the same audience cannot start until the first completes. This serialization constraint affects time-sensitive multi-wave campaign launches where the same audience must be activated to multiple destinations on-demand in rapid succession — each destination activation for the same audience queues behind the previous one.

confidence 85%v1reviewed May 28, 2026aep, activation, ad-hoc, on-demand, system-limit, concurrency, job-serialization, multi-destination

AEP Ad-Hoc Activation — Maximum 1 Concurrent Job Per Audience (System-Enforced)

What it is. Adobe Experience Platform enforces a hard system limit of 1 concurrent ad-hoc activation job per audience at any given time. If an ad-hoc activation job for Audience A is in progress, a second ad-hoc job for Audience A must wait until the first completes before it can start.

Architectural implication. For organizations that need to push the same audience to multiple destinations simultaneously via ad-hoc activation (e.g., activate Audience A to Google DV360, Meta Ads, and Salesforce Marketing Cloud all at once), each destination's ad-hoc job for Audience A queues sequentially. Total activation time scales with the number of destinations, not the number of destinations in parallel.

Interaction with constraint.aep-adhoc-activation-max-audiences-80. Up to 80 distinct audiences can be included in a single ad-hoc activation job. The concurrency limit applies per-audience across jobs, not per-job.

Where the agent should surface this. When a user asks about activating the same audience to many destinations simultaneously via ad-hoc activation — for example, a go-live event triggering suppression across 10 ad platforms — surface this serialization limit and recommend timing expectations based on sequential job throughput.

Sources

Related

← Referenced by

  • governed-byarchetype.aep-heavy-enterprise-evaluating-composable— OC-079. Complements constraint.aep-adhoc-activation-max-audiences-80 for the AEP-heavy enterprise. When the same audience must be activated to multiple destinations in rapid succession via ad-hoc jobs (e.g., suppression sync to 10 ad platforms simultaneously), the 1-concurrent-job-per-audience serialization limit extends total activation time linearly with destination count. Multi-destination rapid-fire activation is a common enterprise requirement during go-live events and emergency suppression workflows.