Dynamic Media (Scene7) bulk asset export or upload fails due to storage and file-size limits
Bulk asset migrations in Dynamic Media (Scene7) - such as Dynamic Media Classic to storage, storage to AEM, or bulk uploads into Scene7 - can fail or run slowly, often without a specific error message. These issues stem from defined processing and file-size boundaries: Dynamic Media Classic limits request batch sizes, Scene7 constrains video file sizes, AEM as a Cloud Service caps per-file ingestion, and the Classic export tool has a throughput ceiling. Exceeding a storage entitlement affects billing rather than functionality, so many of these limits are expected behavior rather than defects.
To fix the issue, compare your files, batches, storage, and throughput against the documented limits and split, throttle, or rebatch the operation accordingly.
Description description
Environment
- AEM Dynamic Media
- Dynamic Media Classic (Scene7)
- Adobe Experience Manager as a Cloud Service
Issue/Symptoms
- Bulk asset export or upload runs significantly slower than expected (for example, below the 25 GB/hour throughput rate).
- Bulk downloads from Dynamic Media Classic fail after roughly 500 assets or 1 GB.
- Large files over 15 GB fail to process in Dynamic Media video pipelines.
- Assets above 30 GB fail to upload when using the AEMaaCS Asset Import Service.
- Metadata preparation for export takes unexpectedly long for very large repositories (for example, about 1.5–2 days for 1.8M assets).
Root cause
Bulk export and ingestion failures generally occur because Dynamic Media and AEM enforce defined processing and file-size boundaries. Dynamic Media Classic limits request batch sizes (500 assets or 1 GB per request), while Dynamic Media (Scene7) enforces file-size and processing constraints (for example, a 15 GB limit for video). AEM as a Cloud Service has a 30 GB per-file limit for some ingestion methods, and metadata extraction becomes slow or unstable for extremely large files (over 15 GB). In addition, the Dynamic Media Classic bulk export tool has a known throughput ceiling (about 25 GB/hour). These operational limits cause slowdowns or failures during large-scale migrations.
Steps to reproduce
- Identify the sizes of the files being exported or ingested and compare them against the limits (Dynamic Media video under 15 GB; AEMaaCS import service up to 30 GB).
- Check whether your Dynamic Media Classic bulk download batches exceed 500 assets or 1 GB per request.
- Measure your current throughput and compare it against the expected 25 GB/hour export rate.
- Estimate the expected metadata-preparation time from your asset count (for example, about 1.5–2 days for 1.8M assets).
Resolution resolution
To fix the issue:
- Check file-size limits. Identify the sizes of the files you are exporting or ingesting and compare them against the verified limits: Dynamic Media video files must be under 15 GB, and the AEMaaCS import service supports files up to 30 GB. If files exceed these limits, split or transcode them before export or ingestion.
- Respect Dynamic Media Classic per-request limits. Keep bulk download batches under 500 assets or 1 GB per request, and break larger migrations into smaller batches that stay within these thresholds.
- Verify your storage entitlements. Confirm your contracted total storage with your account team. AEM as a Cloud Service does not enforce hard storage limits, but exceeding your entitlement affects billing, not functionality. Request temporary capacity if you are near your contractual limit.
- Evaluate throughput of the Dynamic Media Upgrade Tool, if applicable. Measure your current throughput against the expected 25 GB/hour rate. If it is significantly lower, run export jobs with reduced concurrency or throttle operations to reduce bottlenecks.
- Confirm the expected pre-export processing time for large repositories. Estimate metadata-preparation time from your asset count (for example, about 1.5–2 days for 1.8M assets). If it takes much longer, investigate potential API throttling or Scene7-side issues.
- Check the upload path (AEM to Scene7) for performance limits. Review whether upload retries or API failures occur during batch ingestion, and reduce upload concurrency before retrying.
- Rule out download throttling. Dynamic Media (AEM integration) has no built-in throttling or mass-download protection, so implement custom access controls outside Dynamic Media (for example, CDN rules or AEM permissions) if you need to limit high-volume downloads.
- If the issue persists, contact Adobe Support with the total asset count, the file sizes of the failing assets, whether you use Dynamic Media Classic or Dynamic Media with AEM, and throughput logs with timestamps.