---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Workflow engine operation order

# Workflow engine operation order {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

The workflow engine runs in a predefined order relative to business rules and database
operations. It caches commonly-used published workflows to improve performance.

The Run after bus. rules run workflow property defines if a workflow is
Default or Deferred.

The diagram below shows the workflow engine order of operations and when Default and Deferred
flows are executed. For a more general overview of engine operation order, see [Execution order of scripts and engines](https://www.servicenow.com/docs/access?context=r_ExecutionOrderScriptsAndEngines&version=australia&pubname=australia-api-reference&ft:locale=en-US).  
Abbildung : 1. Workflow engine order diagram

## Workflow caching {#ariaid-title2}

The workflow engine caches commonly-used published workflows to improve
performance.

Caching significantly reduces the number of database queries per workflow. By default, the
engine caches up to 300 unique workflow versions. Caching very large workflows may reduce this
number as the cache size cannot exceed the Java Virtual Machine (JVM) heap size.

To change the maximum number of cached workflow versions, navigate to WorkflowAdministrationProperties and modify the value of the The max number of models that will be concurrently held in the LRU cache
(glide.workflow.model.cache.max) property. You must restart the instance to
apply this change.