Use this checklist if there are issues with Acquia DAM assets in Drupal, for example, if they do not update, unpublish, render correctly, or are missing from bulk imports.

• Assets in Drupal do not match changes in Acquia DAM such as status, deletion, metadata, finalized version

  • Confirm that Drupal cron runs regularly.

  • Check whether the DAM media update queue is backed up and, if needed, process it:

    copy

    drush queue:run acquia_dam_media_item_update

  • If many assets appear out of sync, run a bulk asset refresh:

    copy

    drush acquia-dam:update-assets

  • For finalized version changes, queue updates based on the latest finalized versions:

    copy

    drush acquia-dam:queue-update-assets --finalized-version

    Visit the Asset and Metadata updates and Asset status and deletion sections below.

• Pending Delete assets in Acquia DAM still show as Published in Drupal

  • Verify that cron is running and the DAM media update queue has been processed.

  • If needed, run:

    copy

    drush acquia-dam:update-assets

  • For individual items, use Check for update on the DAM media listing in Drupal.

    Visit Asset status and deletion.

• An asset does not render correctly or appears under the wrong media type

  • Check if the Drupal media type matches the actual asset format in Acquia DAM such as image, video, document, archive, and so on.

  • If it looks too generic or incorrect, run:

    copy

    drush acquia-dam:resolve-asset-media-type 

    optionally with --media-type and --batch-size.

  • For SVGs, install and configure the contributed SVG Image module so that SVGs can use image styles.

    Visit Media sources, asset serving, and rendering and Media type resolution and rendering.

• Bulk import misses some expected assets
   
  • Confirm that assets are assigned to the categories or asset groups you configured for import.
  • Imports run in batches through cron, not all assets appear in a single run.

  • Check that assets are released and not expired in Acquia DAM, unreleased or expired assets are intentionally skipped by the bulk import.

    Visit Asset import and management.

• Assets are not provided from the expected domain or file system

  • Check whether Download and sync assets are enabled, if so, assets are provided from the Drupal file system.

  • Confirm that you chose the correct public or private file system before you enable Download and sync, and avoid switching afterward.

    Visit Media sources, asset serving, and rendering.

Troubleshooting checklist