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 configure the workflow run properties on the Advanced Options page in Control Center.
|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. The default is 300 workflows per node.|
|Maximum amount of running workflows in the queue||The number of workflow run requests that the vRealize Orchestrator server accepts before becoming unavailable. The default is 10,000 workflows per node.|
|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. The default is 100 runs per workflow.|
|Log events expiration days||The number of days that log events are kept in the database before they are purged. The default is 15 days.|