![BlogImage.jpg](https://www.initialyze.com/wp-content/uploads/2021/08/disable-workflow-aem.jpg)
Abstract
Adobe Experience Manager has a number of workflows and several of these workflows trigger automatically while performing certain operations such as uploading assets or creating / updating content. The DAM Update Asset workflow for e.g. generates thumbnail renditions, extracts metadata of assets etc. whenever you upload any asset and it’s resource intensive. There are certain times when performing certain large batch operations we don’t want workflows in AEM to kick in as they add additional overhead.
Some common use cases where you may need to disable workflows for e.g:
When backfilling content or syncing Digital Assets or content between environments
Installing packages containing digital assets
Performing large asset ingestions
The workflows are triggered automatically by a Workflow Launcher configuration. While you can individually turn off each workflow, the quickest way to turn off all workflows in AEM is to turn off the launcher itself. In this post we will go over how to quickly disable all workflows in AEM using just a couple of curl commands.
Disable/Enable Workflow Launcher using cURLs:
The following commands can be used to disable all workflow launchers right before any content sync starts and then enable them after it’s over.
A. Disabling Workflow Launcher:
echo "Disable workflow launcher …"
curl http://${aem_user}:${aem_pass}@${target_ip}:${aem_port}/system/console/components/com.adobe.granite.workflow.core.launcher.WorkflowLauncherImpl --data action=disable
curl http://${aem_user}:${aem_pass}@${target_ip}:${aem_port}/system/console/components/com.adobe.granite.workflow.core.launcher.WorkflowLauncherListener --data action=disable
B. Enabling Workflow Launcher:
echo "Enable workflow launcher …"
curl http://${aem_user}:${aem_pass}@${target_ip}:${aem_port}/system/console/components/com.adobe.granite.workflow.core.launcher.WorkflowLauncherImpl --data action=enable
curl http://${aem_user}:${aem_pass}@${target_ip}:${aem_port}/system/console/components/com.adobe.granite.workflow.core.launcher.WorkflowLauncherListener --data action=enable
You can also use the OSGi console to Disabled/Enabled workflow.
Read Full Blog
Q&A
Please use this thread to ask the related questions.
Kautuk Sahni