Adobe's official best practices for Campaign Classic explicitly recommend not exceeding 20 concurrent workflows. Running more than this number simultaneously can severely impact the instance's performance and stability. Excessive concurrent workflows consume significant server resources, including CPU, memory, and database connections, which can lead to processing delays, workflow failures, and overall system degradation. Adhering to this guideline ensures the workflow server (wfserver process) operates efficiently and reliably.

A. 10: This is an unnecessarily low limit. While fewer workflows are better, the platform is designed to handle up to the recommended threshold of 20 without performance issues.

C. 30: This number exceeds the official recommendation and running this many concurrent workflows poses a significant risk to the stability and performance of the Adobe Campaign instance.

D. 50: This is far beyond the recommended limit and would almost certainly lead to severe performance degradation, resource contention, and potential system-wide failures.

1. Adobe Experience League. (2023). Workflow best practices - Adobe Campaign Classic v7 documentation.

Section: General recommendations

Quote: "Do not run more than 20 concurrent workflows."

Reference: https://experienceleague.adobe.com/docs/campaign-classic/using/getting-started/starting-with-workflows/workflows-best-practices.html?lang=en

2. Adobe Experience League. (2023). Production Guide - Monitoring recommendations - Adobe Campaign Classic v7 documentation.

Section: Workflows

Content: This section discusses monitoring workflow statuses (wfserver module) and emphasizes that a high number of workflows in a "Started" state can indicate performance issues

indirectly supporting the need for a limit on concurrent executions.

Reference: https://experienceleague.adobe.com/docs/campaign-classic/using/production-procedures-and-technical-recommendations/production-guide/monitoring-recommendations.html?lang=en#workflows