An AEM server is overloaded with too many concurrently running workflows. The developer decides to reduce the number of concurrent workflows. What should be configured?

The AEM workflow engine processes workflow steps as jobs in a queue. The "Granite Workflow Queue" is the OSGi service responsible for managing this queue and its execution. To control the number of concurrently running workflows and manage server load, an administrator must configure the "Maximum Parallel Jobs" property within this service. Lowering this value reduces the number of threads in the workflow job processing pool, thereby decreasing the number of workflows that can execute simultaneously.

B. Launchers for each workflow: Workflow launchers are triggers that initiate a workflow based on repository events. Modifying launchers controls when or if workflows start, not how many run concurrently once they are in the queue.
C. The number of threads in scheduler: This configures the general-purpose Apache Sling Scheduler. While workflows may use it for some operations, the primary workflow job execution is managed by its own dedicated "Granite Workflow Queue" service, not the general scheduler pool.

1. Adobe Experience Manager Documentation - Administering Workflows: "To control the number of concurrently running workflow processes, you can configure the Granite Workflow Queue... The property to configure is Maximum Parallel Jobs."

Source: Adobe Experience League, "Administering Workflows," section "Configure the Granite Workflow Queue."

2. Adobe Experience Manager Documentation - Performance Tuning Tips: "Workflow Overload: If your instance is overloaded with too many workflows, you can configure the Granite Workflow Queue service. Set the Maximum Parallel Jobs property to a lower value."

Source: Adobe Experience League, "Performance Tuning Tips," section "Workflow Performance."

3. Adobe Experience Manager Documentation - OSGi Configuration Settings: The com.adobe.granite.workflow.core.jcr.WorkflowManager service, configured via the PID org.apache.sling.event.jobs.QueueConfiguration.granite/workflow/queue, contains the queue.maxparallel property ("Maximum Parallel Jobs"). This setting directly defines the size of the thread pool for the workflow queue.

Source: Adobe Experience League, "OSGi Configuration Settings," search for "Granite Workflow Queue."