Resolving performance delays and repeated data import job failures in Adobe Experience Manager
This article explains how to resolve performance delays and repeated data import job failures in Adobe Experience Manager (AEM) by reviewing system health and adjusting import job size and sequencing.
Description description
Environment
Adobe Experience Manager (all versions)
Issue/Symptoms
Large or concurrent imports place excessive load on Adobe Experience Manager and cause performance delays and repeated data import job failures.
The following symptoms occur:
- Import jobs fail and restart automatically.
- Multiple workflow instances for the same import appear in logs.
- AEM environment responsiveness degrades during import attempts.
Cause
High processing load from large or concurrent import jobs causes workflow restarts and performance degradation. Splitting imports into smaller, sequential batches reduces system strain and prevents repeated failures.
Resolution resolution
Follow these steps to resolve the issue:
- Review the workflow history and system logs to confirm that no server restarts or system health-check failures occur during import attempts.
- Ensure that only one import job runs at a time and that no concurrent imports are running.
- If you are importing a large set of entities, split the import into smaller batches to reduce processing load.
- Run the smaller imports sequentially, allowing each workflow to complete on the import status page before starting the next import.
- Monitor the environment’s responsiveness and workflow logs during each import to ensure stability.
- If the issue persists, further investigate custom workflow implementations or API integrations for unexpected behavior.
To verify the resolution, confirm that imports complete successfully without repeated restarts and that system responsiveness is restored during import operations.