Show Menu
TOPICS×

Asynchronous operations

To reduce adverse impact on performance, Adobe Experience Manger Assets processes certain long-running and resource-intensive asset operations asynchronously.
These operations include:
  • Deleting many assets
  • Moving many assets or assets with many references
  • Exporting/importing asset metadata in bulk.
  • Fetching assets, that are above the threshold limit set, from a remote Experience Manager deployment.
Asynchronous processing involves enqueuing multiple jobs and eventually running them in a serial manner subject to the availability of system resources.
You can view the status of asynchronous jobs from the Async Job Status page.
By default, jobs in Assets run in parallel. If N is the number of CPU cores, N/2 jobs can run in parallel, by default. To use custom settings for the job queue, modify the Async Operation Default Queue configuration from the web console. For more information, see queue configurations .

Monitor the status of asynchronous operations

Whenever Assets processes an operation asynchronously, you receive a notification at your inbox and through email.
To view the status of the asynchronous operations in detail, navigate to the Async Job Status page.
  1. In the Experience Manager interface click Operations > Jobs .
  2. In the Async Job Status page, review the details of the operations.
    To ascertain the progress of a particular operation, see the value in the Status column. Depending upon the progress, one of the following statuses is displayed:
    • Active : The operation is being processed
    • Success : The operation is complete
    • Fail or Error : The operation could not be processed
    • Scheduled : The operation is scheduled for processing a later time
  3. To stop an active operation, select it from the list and click Stop from the toolbar.
  4. To view extra details, for example description and logs, select the operation and click Open from the toolbar.
    The job details page is displayed.
  5. To delete the operation from the list, select Delete from the toolbar. To download the details in a CSV file, click Download .
    You cannot delete a job if its status is either active or queued.

Purge completed jobs

Experience Manager Assets runs a purge job everyday at 1:00 AM to delete completed asynchronous jobs that are more than a day old.
You can modify the schedule for the purge job and the duration for which details of completed jobs are retained before they are deleted. You can also configure the maximum number of completed jobs for which details are retained at any point of time.
  1. In the Experience Manager interface click Tools > Operations > Web Console .
  2. Open the Adobe CQ DAM Async Jobs Purge Scheduled job.
  3. Specify the threshold number of days after which completed jobs are deleted and the maximum number of jobs for which details are retained in history.
  4. Save the changes.

Configure thresholds for asynchronous processing

You can configure the threshold number of assets or references for Assets to process a particular operation asynchronously.

Configure thresholds for asynchronous delete operations

If the number of assets or folders to be deleted exceed the threshold number, the delete operation is performed asynchronously.
  1. In the Experience Manager interface click Tools > Operations > Web Console .
  2. From the web console, open the Async Delete Operation Job Processing configuration.
  3. In the Threshold number of assets box, specify the threshold number of assets/folders for asynchronous processing of delete operations.
  4. Save the changes.

Configure thresholds for asynchronous move operations

If the number of assets/folders or references to be moved exceed the threshold number, the move operation is performed asynchronously.
  1. In the Experience Manager interface click Tools > Operations > Web Console .
  2. From the web console, open the Async Move Operation Job Processing configuration.
  3. In the Threshold number of assets/references box, specify the threshold number of assets/folders or references for asynchronous processing of move operations.
  4. Save the changes.