AJO Batch Audience shows 0 qualified profiles even though profiles exist and journey doesn't start | Community
Skip to main content
M
MandeepSi9
Level 1
July 27, 2026
Question

AJO Batch Audience shows 0 qualified profiles even though profiles exist and journey doesn't start

  • July 27, 2026
  • 1 reply
  • 32 views

I created:

  • Profile-enabled Schema
  • Profile-enabled Dataset
  • Identity configured (Email namespace)
  • Ingested customer data successfully
  • Profiles are visible under Real-Time Customer Profiles
  • Created a Batch Audience using Email Address
  • Created a Journey using Read Audience as the entry activity

However, the audience always shows:

Qualified Audience Size = 0

As a result, no profiles enter the journey.

 

What I have already verified

Schema & Dataset

  • Profile-enabled schema
  • Profile-enabled dataset
  • Data ingestion completed successfully
  • No failed batches in the current dataset

Profiles

The profile exists and contains:

  • Email Address
  • First Name
  • Last Name
  • Identity Map

Audience

  • Audience is Published
  • Origin = Segmentation Service
  • Evaluation Type = Batch
  • Population remains 0

 

Monitoring

In Monitoring I noticed:

  • Last Evaluation Job = No runs (for multiple audiences)
  • Last Activation Job = No runs

Even after waiting more than 24 hours, no evaluation job appears.

AI Assistant Findings

I also checked using AJO AI Assistant.

It confirmed:

  • Audience Type = Batch
  • Total Profiles = 0
  • No destinations activated
  • No explicit errors returned

AI Assistant suggested checking:

  • Identity namespace alignment
  • Profile snapshot generation
  • Segmentation export
  • Batch evaluation timing

Identity namespace has already been verified.

ox or development sandbox?

Any suggestions would be greatly appreciated.

Thank you!

 

1 reply

Pulkit_Jain_
Adobe Employee
Pulkit_Jain_Adobe Employee
Adobe Employee
July 27, 2026

​@MandeepSi9 Your setup seems correct, so the key issue is could be that the segmentation/export pipeline is not running in your sandbox.

The key issue is that “Last Evaluation Job = No runs” and “Last Activation Job = No runs”. This means the batch evaluation was never generated and profile snapshot required for AJO Read Audience.

The most likely causes are a stuck or missing segmentation scheduler, a missing profile snapshot export job, or a sandbox provisioning/reset issue, which is common in dev sandboxes.

Quick checks:

  • Run “Evaluate audience now” (Flexible Audience Evaluation)
  • Verify segment jobs exist
  • Check profilesnapshot* system datasets
  • Confirm journey namespace = Email

Suggest checking in the AEP ExL forum

M
MandeepSi9Author
Level 1
July 27, 2026

Hi ​@Pulkit_Jain_ 

Thank you for your suggestions.

Here are my findings after checking the environment:

Audience Evaluation: The Monitoring dashboard shows that the Last Evaluation Job = Failed (not "No runs"). This indicates that an evaluation job is being created, but it is failing.Fyr I also attached a Screenshot

Flexible Audience Evaluation: This option is not available in my sandbox, so I'm unable to manually trigger an audience evaluation.but to overcome this I have also try with Streaming.

Profile Snapshot System Datasets: I could not verify the profile_snapshot* system datasets because they are not visible in my envirement

Thanks
Mandeep Singh

Pulkit_Jain_
Adobe Employee
Pulkit_Jain_Adobe Employee
Adobe Employee
July 27, 2026

Your latest findings confirm this is no longer a configuration issue.

Since the “Last Evaluation Job = Failed”, AEP is attempting to run the audience evaluation but the segmentation/export process is failing before the profile snapshot is generated. That is why the audience count remains 0 and the Read Audience journey never starts.

The fact that Flexible Audience Evaluation is unavailable and profilesnapshot* datasets are not visible strongly points to a sandbox/backend provisioning or segmentation service issue rather than schema, identity, or ingestion configuration.

At this stage, the best next step is to raise an Adobe Support ticket.

Terms & ConditionsAccessibility statement

Loading footer...