Records getting received but not ingested in AEP | Community
Skip to main content
S
ShivaniM
Level 3
October 16, 2023
Solved

Records getting received but not ingested in AEP

  • October 16, 2023
  • 2 replies
  • 1720 views

Hi Team,

 

For mobile push notifications, we have created a datastream to add the data in AEP.

However, in source dataflow, I'm able to see dataflow runs and records received but not ingested. Could you help me with the reason and how can we rectify it.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arpan-garg

Hi @shivanim  It can be an issue if you are not passing dataflow id or schema details. Can you please send me the request.

If in HTTP streaming API we create a single connection and in that single connection we have created an api for multiple datasets, then passing schema details or dataflowid is mandatory for the tool to understand for which dataset the request is for.

When we don't pass those details we get 200 status code which makes it looks like it passed but we never get the data.

2 replies

Rudi-Shumpert
Adobe Employee
Rudi-ShumpertAdobe Employee
Adobe Employee
October 16, 2023

Did you create the XDM Schema & the corresponding dataset?  Check in the ingestion & validation on the dataset to see if there is any data coming in or if there are any errors listed. 

    arpan-garg
    Community Advisor
    arpan-gargCommunity Advisor
    Community Advisor
    October 17, 2023

    Hi @shivanim - When you say records are not ingested, do you get some ingestion errors in AEP? If not, how are you checking if data is ingested or not?

     

    Thanks,

    Arpan

    S
    ShivaniMAuthor
    Level 3
    October 20, 2023

    Hello, 

    I also raised a ticket with Adobe to check the issue closely, they updated:
    the missing details of batches on that dataset, and ingestion metrics on the dataflows is a limitation with this type of ingestion. While not ideal, it does not necessarily indicate any issue.

    Thank you!

      arpan-garg
      Community Advisor
      arpan-gargCommunity AdvisorAccepted solution
      Community Advisor
      October 20, 2023

      Hi @shivanim  It can be an issue if you are not passing dataflow id or schema details. Can you please send me the request.

      If in HTTP streaming API we create a single connection and in that single connection we have created an api for multiple datasets, then passing schema details or dataflowid is mandatory for the tool to understand for which dataset the request is for.

      When we don't pass those details we get 200 status code which makes it looks like it passed but we never get the data.

        Terms & ConditionsAccessibility statement

        Loading footer...