Skip to main content
OmarGo2
Level 2
Jan 20, 2026 10:11 PM UTC
Solved

Batch Ingestion Error INGEST-1211-400: Why does formatted JSON fail but JSONL succeeds?

Hello Adobe Community,

I'm experiencing an inconsistent behavior with batch data ingestion in AEP and would like to understand the underlying technical reasons.

Issue: When uploading data via the UI to a Profile-enabled dataset, I'm getting error INGEST-1211-400 with formatted JSON, but the same data succeeds when converted to JSONL (newline-delimited JSON).

Error Details:

  • Error Code: INGEST-1211-400
  • Description: "An error occurred while processing the batch. Please contact support."
  • Error Code: 150 - "Parsing errors occurred when converting or validating the data"
  • Records received: 0
  • Records ingested: 0


    What works:

    {"_id":"/profile/0001","personID":"000000000001","person":{"name":{"firstName":"Luis"}},"personalEmail":{"address":"user@example.com"}}

    What fails:

    {
      "_id": "/profile/0001",
      "personID": "000000000001",
      "person": {
        "name": {
          "firstName": "Luis"
        }
      },
      "personalEmail": {
        "address": "user@example.com"
      }
    }
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
AshuDw4Accepted solution
Level 2
Jan 21, 2026 5:33 AM UTC

Hi, while uploading a batch file into dataset. Always use one-line JSON format. With multi line JSON it shows the error.

View in thread

4 replies

AshuDw4Accepted solution
Level 2
Jan 21, 2026 5:33 AM UTC

Hi, while uploading a batch file into dataset. Always use one-line JSON format. With multi line JSON it shows the error.

Translate
    giriprasathb
    giriprasathb
    Level 3
    Jan 21, 2026 7:24 AM UTC

    Hello ​@OmarGo2 ,

    The behavior you are seeing is expected due to how Adobe Experience Platform (AEP) batch ingestion processes data.

    • Issue: When uploading standard JSON via the UI, AEP expects newline-delimited JSON (JSONL) for batch ingestion. A JSON array or single JSON object cannot be parsed as multiple records in a batch. This causes the INGEST-1211-400 error with code 150: “Parsing errors occurred when converting or validating the data.”

    • Why JSONL works: In JSONL, each line is treated as a separate record. The ingestion service can parse each line individually, allowing successful ingestion.

    Example:

    ✅ JSONL (works):

     

    {"_id":"/profile/0001","personID":"000000000001","person":{"name":{"firstName":"Luis"}},"personalEmail":{"address":"user@example.com"}}


    ❌ Standard JSON (fails):

     

    { "_id": "/profile/0001", "personID": "000000000001", "person": { "name": { "firstName": "Luis" } }, "personalEmail": { "address": "user@example.com" } }


    Recommendation:

    Always use JSONL format for batch ingestion to Profile-enabled datasets in AEP. Each line represents a single record, ensuring that the ingestion parser can handle the data correctly.


    References:

    https://jsonlines.org/

    Thanks,
    Giriprasath B

    Translate
    amruta1412
    Level 2
    Jan 21, 2026 8:26 AM UTC

    ​@OmarGo2 Batch data ingestion in AEP does not support multi-line json via UI upload. Incase you are ingesting through Batch Ingestion API and using multiline json, you can set “ismultilineJson=true”.  https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/batch/troubleshooting 

     

    Translate
      Sukrity_Wadhwa
      Sukrity_Wadhwa
      Level 4
      Jan 29, 2026 9:18 AM UTC

      Hi ​@OmarGo2, 

      Were you able to resolve this query with the help of the provided solutions, or do you still need further assistance? Please let us know. If any of the answers were helpful in moving you closer to a resolution, even partially, we encourage you to mark the one that helped the most as the 'Best Answer'.

      Thank you!

      Translate
      Sukrity Wadhwa
      Terms & ConditionsAccessibility statement

      Loading footer...