Issues with uploading assets in DAM | Community
Skip to main content
T
test1234567
Level 6
May 6, 2024
Solved

Issues with uploading assets in DAM

  • May 6, 2024
  • 2 replies
  • 845 views

Hello Community - I see some issues in uploading the assets in DAM. After uploading the assets, the thimbnail logo, preview and the metadata is blank. If I manuall trigger the DAM update assets workflow, the uploaded image preview is loading fine along with the metadata. The issue is with the triggering the workflow while uploading the assets. I can confirm there is no change happened in the OOTB workflow. I have even checked the permissions of workflow-user. I don't see any errors in the log. Can someone tell me what could be the issue?

 

 

 

@joerghoh 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by HrishikeshKagne

Hi @test1234567 ,

  1. Event Listener Configuration: Check if there are any custom event listeners or configurations that might interfere with the asset upload workflow triggering. Sometimes, customizations can unintentionally affect the triggering of workflows upon asset upload.

  2. Dispatcher Configuration: If you are using Adobe Dispatcher in front of your AEM instance, ensure that the cache settings are not preventing the triggering of the workflow. Sometimes, aggressive caching configurations can delay or prevent the triggering of workflows.

  3. Asset Workflow Configuration: Review the DAM Update Asset workflow configuration to ensure that it's correctly set up. Check if there are any customizations or configurations that might be causing the issue. Pay attention to any conditions or preconditions that could prevent the workflow from being triggered automatically upon asset upload.

  4. Logging: Although you mentioned that you haven't found any errors in the logs, it's still worth checking the logs again thoroughly. Look for any warnings or errors that might indicate issues related to asset upload or workflow triggering.

  5. Replication Issues: Ensure that replication agents are configured correctly and that there are no issues with replication between author and publish instances, if applicable. Sometimes, replication issues can affect the triggering of workflows.

  6. Dispatcher Flush: Manually trigger a cache flush on the Dispatcher to ensure that any changes made are reflected immediately. This can help rule out caching issues as a potential cause.

  7. AEM Version Compatibility: Ensure that the AEM version you're using is compatible with your configuration and any customizations you've made. Sometimes, issues arise due to compatibility issues between AEM versions and configurations.

If you've exhausted these options and are still unable to resolve the issue, it might be beneficial to reach out to Adobe Support or consult with experienced AEM developers for further assistance. They may be able to provide more specific guidance based on your environment and configurations.

2 replies

HrishikeshKagne
Community Advisor
HrishikeshKagneCommunity AdvisorAccepted solution
Community Advisor
May 7, 2024

Hi @test1234567 ,

  1. Event Listener Configuration: Check if there are any custom event listeners or configurations that might interfere with the asset upload workflow triggering. Sometimes, customizations can unintentionally affect the triggering of workflows upon asset upload.

  2. Dispatcher Configuration: If you are using Adobe Dispatcher in front of your AEM instance, ensure that the cache settings are not preventing the triggering of the workflow. Sometimes, aggressive caching configurations can delay or prevent the triggering of workflows.

  3. Asset Workflow Configuration: Review the DAM Update Asset workflow configuration to ensure that it's correctly set up. Check if there are any customizations or configurations that might be causing the issue. Pay attention to any conditions or preconditions that could prevent the workflow from being triggered automatically upon asset upload.

  4. Logging: Although you mentioned that you haven't found any errors in the logs, it's still worth checking the logs again thoroughly. Look for any warnings or errors that might indicate issues related to asset upload or workflow triggering.

  5. Replication Issues: Ensure that replication agents are configured correctly and that there are no issues with replication between author and publish instances, if applicable. Sometimes, replication issues can affect the triggering of workflows.

  6. Dispatcher Flush: Manually trigger a cache flush on the Dispatcher to ensure that any changes made are reflected immediately. This can help rule out caching issues as a potential cause.

  7. AEM Version Compatibility: Ensure that the AEM version you're using is compatible with your configuration and any customizations you've made. Sometimes, issues arise due to compatibility issues between AEM versions and configurations.

If you've exhausted these options and are still unable to resolve the issue, it might be beneficial to reach out to Adobe Support or consult with experienced AEM developers for further assistance. They may be able to provide more specific guidance based on your environment and configurations.

Hrishikesh Kagane
    aanchal-sikka
    Community Advisor
    aanchal-sikkaCommunity Advisor
    Community Advisor
    May 7, 2024

    @test1234567 

     

     Please validate the workflow launcher. An asset upload should kick off

    • "Dam Update Asset workflow" for AEM 6.5
    • "Asset Processing on SDK" for AEMaaCS SDK. 

     

    Attaching a screenshot from AEMaaCS SDK

     

     

    Once launcher is validated, upload Asset and check error.log. Do you have logs related to the above workflows?

     

     

    Aanchal Sikka
      Terms & ConditionsAccessibility statement

      Loading footer...