Skip to main content
GK-007
Level 9
March 25, 2026
Question

Is there any AEP API available to retrieve the failed data ingestion batch?

  • March 25, 2026
  • 2 replies
  • 71 views

Hello all,

We have standard setup in AEP to collect the event data for our application, don’t have any source and destination model to ingest data. I want to setup any alert system when there is any data ingestion failure. Is there any OOTB alert system provided by Adobe itself to trigger emails or is there any api to check if there are any failed batches to recursively?

If anyone come across this kind of requirements or done already implementation, please help me.I have gone through the below link but it’s not working for us.

Thank you in advance!

-Kishore

    2 replies

    Gokul_Agiwal
    Community Advisor
    Community Advisor
    March 25, 2026

    Hi ​@GK-007 

    As far as I know, Adobe doesn’t provide any OOTB alerting system for ingestion failures. However the official documentation describes how to retrieve ingestion diagnostics using APIs; 

    https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/quality/error-diagnostics 

    So in this case, you can implement your own monitoring system using ingestion API - which has state / status https://experienceleague.adobe.com/en/docs/experience- platform/ingestion/batch/troubleshooting#batch-states 

    https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/batch/troubleshooting#how-is-batch-ingestion-monitored 

    GK-007
    GK-007Author
    Level 9
    March 25, 2026

    Thank you ​@Gokul_Agiwal for sharing details. I have already reviewed these APIs and majority of them fetch the details of the batch when we give batch id in the input but our use case is, wanted to trigger an alert when there is any data ingestion fail is identified. I have setup these APIs already in Postman, and able to retrieve the failed batch details.

     

    Level 2
    April 1, 2026

    Hi ​@GK-007 

     

    This is a critical requirement for maintaining data health. While there isn't a single 'switch' to flip, you can achieve a robust alerting system using a combination of Observability Insights and the Catalog API.

    1. OOTB Alerting System (Email & UI)
    Adobe provides an Alerts feature within AEP that is specifically designed to eliminate the need for manual polling. 

    • How to set it up: Navigate to Administration > Alerts in the left navigation.
    • Subscribe to Failure Rules: Look for rules like 'Sources Ingestion Error Rate Exceeded' or 'Ingestion Failure'.
    • Email Notifications: As an admin, you can 'Manage Subscribers' for these rules to add your email or a team DL. You must also enable 'Instant notifications' in your Experience Cloud Preferences to receive the emails. 

    2. API for Recursive Checking (Catalog API)
    If you want to build a custom monitoring script (like in a Lambda or Jenkins job) to check for failed batches periodically, use the Catalog API

    • The Endpoint: GET /data/foundation/catalog/batches
    • The Filter: You can filter by status=failed and use a createdAfter parameter to only look at the last few hours.
      • Example call: https://adobe.io (using a Unix timestamp).
    • Retrieve Error Details: Once you have a failed batchId, use the Data Ingestion API with the diagnostics endpoint to get the specific reason for failure:
      • GET /data/foundation/import/batches/{BATCH_ID}/diagnostics 

    3. Advanced: Real-time Webhooks via Adobe I/O
    If you need near real-time alerts in Slack or Teams, you should subscribe to Adobe I/O Events.

    • In the Adobe Developer Console, add the 'Platform Notifications' event to your project.
    • Configure a Webhook to listen for ingestion_failure events. This will push a JSON payload to your endpoint the moment a batch fails, allowing for instant automated triage. 

    Recommendation: Start with the OOTB Alerts for immediate email visibility, then use the Catalog API if you need to build a custom dashboard or automated retry logic

     

    Thanks,

    Santosh Kumar

    Santosh Kumar | AEP & CJA Expert
    GK-007
    GK-007Author
    Level 9
    April 1, 2026

    Thanks ​@santoshkr ,i have already set the OOTB alerts now, needs test this. I think problem with approach is if the failure rate is more than 1% only alerts will be triggered. I will check other options as well, if the OOTB not working. Thanks for sharing the details, they are helpful.

    Level 2
    April 1, 2026

    Hi ​@GK-007 

    You’re absolutely right—the 1% threshold can be a 'blind spot' for smaller, critical data gaps. If you need 100% visibility even for a single failed batch, here is the workaround:

    1. Create a Custom 'Threshold' Alert:
    In the Alerts UI, instead of using the 'OOTB' system-wide rules, you can sometimes create a custom rule (depending on your license tier) where you set the threshold to > 0%. This ensures that even one failed ingestion triggers the notification.

    2. The 'Pro' Solution: Adobe I/O Events (0% Threshold)
    If the UI alerts aren't granular enough, I highly recommend the Adobe I/O Event approach I mentioned earlier.

    • Why: Unlike the UI alerts, Adobe I/O doesn't care about 'percentages.' It fires a webhook for every single ingestion_failure event.
    • Action: You can point this webhook to a simple Logic App, Zapier, or Slack/Teams connector. You will get a notification the second a batch fails, regardless of the failure rate.

    3. API Monitoring (The 100% Reliable Audit):
    If you go the API route, you can run a daily 'Health Check' script:
    GET /data/foundation/catalog/batches?status=failed&createdAfter={24_hours_ago}
    If the API returns any results (count > 0), have your script send an internal alert. This is the only way to be 100% sure you didn't miss a single record.

    Try the Adobe I/O webhook if you want 'Instant' alerts without the 1% restriction!

     

    Thanks,

    Santosh Kumar

    Santosh Kumar | AEP & CJA Expert