ACS AEM Commons Bulk Workflow Manager not working properly for DAM Update Asset Workflow

[BinaryAlchemy11]

I have a requirement for creating multiple renditions for asset on upload. Hence, I have modified the OOTB DAM Update Asset Workflow to create multiple web renditions. The workflow runs fine on the assets. I was trying to use AEM ACS Commons Bulk Workflow Manger to run the workflow on the existing assets which are in millions. The issue I am facing is while using the Bulk Workflow Manager, selecting Bulk Workflow Runner > AEM Workflow, the renditions gets created properly. Whereas on selecting Bulk Workflow Manager > Synthetic (Single Threaded) or Synthetic (Multiple Threaded), the renditions doesn't get created properly although the Workflow execution is completed for all the assets.

To replicate the issue:

AEM Version: 6.5.20

ACS AEM Commons: 6.2.0 / 6.5.0 (Tested with both versions)

1. Add web rendition creation step in DAM Update Workflow

2. Make the DAM Update Workflow as NON-TRANSIENT (To have the logs track on workflow execution)

2. Use ACS AEM Commons, Bulk Workflow Manager to execute on the folder of assets. 

3. Select Synthetic (Single Threaded and Multi Threaded)  to test on the assets.

4. Check the asset renditions and test again selecting AEM Workflow dropdown selection in Bulk Workflow Manager page.

Any recommendation and suggestion to avoid this issue. I have seen that the recommendation for large scale assets workflow execution with Bulk Workflow Manager is to go with the Synthetic Workflow (Multi Threaded).

Note: I am intending to run the modified DAM Update Workflow with Bulk Workflow Manager with having much stress to the inhouse AEM server.

If there is any version of ACS Common that doesn't have this issue with the Synthetic Workflow (Single Threaded and Multi Threaded) that would really be helpful. 

[EstebanBustamante]

Hi, 

Is there any update made to the other 'DAM Update Asset' model that could potentially hit any of these limitations? https://adobe-consulting-services.github.io/acs-aem-commons/features/synthetic-workflow/index.html#s.... Are you seeing any errors in the logs? Have you tried running it using the 'Transient' option?

[BinaryAlchemy11]

The only think added to the 'DAM Update Asset' model is with the following 3 steps for the different renditions creation which I have checked should not have hit any of the limitation given in https://adobe-consulting-services.github.io/acs-aem-commons/features/synthetic-workflow/index.html#s....

I haven't yet seen any relevant errors. Also, I haven't tried transient option yet as I wanted to keep track of the assets that have the workflow been completed and the assets that have failed the workflow.

[BinaryAlchemy11]

Would you be able to try it on your end with the same version of the AEM ACS Commons Package for the Synthetic (Single/Multi Threaded) runner modifying the DAM Update Workflow with rendition creation step added in there please?

[kautuk_sahni]

@BinaryAlchemy11 Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

[BinaryAlchemy11]

The issue has not been resolved yet. Still looking for some suggestion/recommendation to get this issue figured out with AEM ACS Commons - Bulk Workflow Manager.