Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Data ingestion - Data Landing Zone debugging

Avatar

Level 10

If I ingest data to landing zone how can I debug:

1. How to access manifest file for the specific dataflow run id?

2. Is to access my flow-id for the specific dataflow run id? In order to preview how many profiles were ingested etc?

https://experienceleague.adobe.com/en/docs/experience-platform/sources/api-tutorials/monitor

Why Adobe cannot make such a tutorial step by step ...

 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

4 Replies

Avatar

Level 6

@Michael_Soprano I guess this for Data landing zone destination connector, was the Include manifest file Toggle enabled when the Connector was configured? if so you should be able to see a manifest file (sample here) with Data Flow ID and size info.

Avatar

Level 10

Do you know if I can download the manifest file for data ingestion for Data Landing Zone source connector? In the UI there is a curl

Michael_Soprano_0-1760196465431.png

If I follow the instructions then at the final request I got the file with data but not the manifest .... (its dummy data 🙂

Michael_Soprano_1-1760196587429.png

 

 

Avatar

Administrator

Hi @Devyendar,

Would you be able to support @Michael_Soprano further on this? 

Thanks!



Sukrity Wadhwa

Avatar

Level 6
@Michael_Soprano I got more clarity on your question. My earlier response was more towards getting Manifest file (directly in Data Landing Zone) in the Destination connection.
But I realize now that your question is on DLZ Source connector. For source connector you can get the Manifest file path through API.
 
Based on Data Flow ID: 
Look for Manifest file path in the response: 
 "fileSummary": {
"inputFileCount": 2,
    "outputFileCount": 1,
    "extensions": {
        "manifest": {
        }
    }
},
"statusSummary": {
    "status": "success",
    "errors": [
        {
            "code": "CONNECTOR-2001-500",
            "message": "Error occurred at promotion activity."
        }
    ],
    "extensions": {
        "manifest": {
        },
 
 
Look for similar Manifest path in File summary object in the response.
 
Hope this provides the solution you are looking for.