By default, you can run up to 300 workflows per node, and up to 10,000 workflows can be queued if the number of actively running workflows is reached.
When the vRealize Orchestrator node has to run more than 300 concurrent workflows, the pending workflow runs are queued. When an active workflow run completes, the next workflow in the queue starts to run. If the maximum number of queued workflows is reached, the next workflow runs fail until one of the pending workflows starts to run.
You can modify these workflow run characteristics by configuring the workflow run properties.
|Enable safe mode||If safe mode is enabled, all running workflows are canceled and are not resumed on the next vRealize Orchestrator node start.|
|Number of concurrent running workflows||The number of workflows that run simultaneously.|
|Number of concurrent running workflows||The number of workflow run requests that the vRealize Orchestrator server accepts before becoming unavailable.|
|Maximum number of preserved runs per workflow||The maximum number of finished workflow runs that are kept as history per workflow. If the number is exceeded, the oldest workflow runs are deleted.|
|Log events expiration days||The number of days that log events are kept in the database before they are purged.|
|Option||System property||Default value|
|Enable safe mode||ch.dunes.safe-mode||false|
|Number of concurrent running workflows||com.vmware.vco.workflow-engine.executors-count||300|
|Maximum amount of running workflows in the queue||com.vmware.vco.workflow-engine.executors-max-queue-size||10000|
|Maximum number of preserved runs per workflow||ch.dunes.task.max-workflow-tokens||100|
|Log events expiration days||com.vmware.o11n.log-events-expiration-days||15|