Resolving asset transfer errors from Workfront to Adobe Experience Manager
This article explains how to resolve asset transfer failures between Adobe Experience Manager (AEM) and Workfront when using the Native Connector. Assets fail to transfer to linked AEM folders and return a status code 400 with the error unable to send documents to external storage. To resolve the issue, remove unsupported characters and retry the transfer.
Description description
Environment
- Adobe Experience Manager (AEM) integrated with Workfront via the Native Connector
Issue/Symptoms
- Assets do not appear in the linked AEM folder after transfer attempts.
- Error message: unable to send documents to external storage.
- A 400 status code is returned during the transfer process.
- Asset transfers are slow or remain stuck.
- The issue affects multiple assets or projects.
Root cause
Unsupported characters in project names, folder names, or asset file names prevent successful asset transfers. Naming restrictions enforced by AEM and the Native Connector block the transfer process.
Resolution resolution
Follow the steps below to resolve the issue.
- Review all project names, folder names, and asset file names involved in the transfer from Workfront to AEM.
- Remove or replace unsupported characters in the names. Common unsupported characters include *, /, :,
[, ,], |, #, %, {, }, ?, ", ., , ;, +, &, and tab characters. - After updating the names, retry the asset transfer using the AEM Native Connector.
- If the issue persists, clear the Workfront cache and verify that all required workflow tags are present and configured correctly.
- Review the AEM documentation for folder and asset naming restrictions to ensure that all names comply with supported conventions.
- Verify the resolution by confirming that the asset transfer completes successfully and that the assets appear in the linked AEM folder.
recommendation-more-help
experience-cloud-kcs-help-kbarticles