{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":22167,"path":"integrate-applications/system-export-sets/parallel-exports.md","title":"Parallel exports","bundle":null,"doc_type":null,"release":"australia","body":"\n# Parallel exports\n\nSplit outgoing data into multiple export sets and process them in parallel to reduce processing time.\n\nUse parallel exports when exports take a long time due to large datasets with time-consuming scripts.\n\nParallel export is most effective for exports with 50,000 or more records. This is controlled by the **glide.scheduled\\_export.min\\_rows\\_for\\_parallel\\_export** property \\(default = 50,000\\). If your export has fewer rows than this threshold, the system automatically uses standard export processing.\n\n## How parallel exports work\n\nWhen you enable parallel export, the system splits the data into multiple chunks and processes them concurrently. The number of chunks processed depends on available worker threads in the parallel job queue. Each chunk is queued as a separate Parallel Export Set Job and processed as worker threads become available.\n\nParallel export set jobs are processed via a shared queue. Processing depends on:\n\n1.  Available worker threads in the job queue\n2.  Queue polling and job pickup by available workers\n3.  Concurrent execution as worker threads become available\n\nAll jobs run concurrently, depending on the availability of worker threads.\n\n## Parallel export record structure\n\nEach parallel export creates a Parallel Export Set record. The form view shows:\n\n-   All related export sets\n-   Parallel export set jobs\n-   Export histories\n\nBy default, parallel export requires 50,000 rows. This threshold enables parallel processing to be used only for large datasets where it provides significant performance benefits.\n\nTo customize this threshold, create the system property **glide.scheduled\\_export.min\\_rows\\_for\\_parallel\\_export** with an integer value.\n\nWhen the export runs with parallel export enabled:\n\n-   A parallel export set record is created with a PES prefix \\(for example, `PES010001`\\)\n-   Multiple parallel export-set job records are created, one per chunk, with a PESJ prefix \\(for example, `PESJ010001`, `PESJ010002`\\)\n-   Multiple export history records are created, one per chunk\n-   Each export history record contains an exported file attachment\n\nThe **Parallel Export Set** and **Parallel Export Set Job** fields on the export history records link back to the parallel export set and individual jobs.\n\nFiles from parallel exports are stored on the MID Server in a parallel sub-folder: `{MID_Server}/agent/export/parallel/{configured_path}/`. File naming format includes the parallel export set number, export set name, timestamp, and sequential file number: For example: `PES0100001_incident__20251204001638_1.xlsx`. The file number increments for each chunk \\(\\_1, \\_2, \\_3, and so on\\).\n\n"}}