Cora Knowledge Center

Support

Configure workflow persistence

Overview

During workflow execution, activity instance-related database queries are combined and sent in batches. This setup reduces the number of queries to the database and improves system performance.

Configure the buffer size

You can configure buffer parameters in theconfigfile of the application or service that uses the Cora SeQuence database: Administration, Flowtime, Background Runtime Service (BRS), and Job Execution Service (JES). 

Parameters

ParameterDescription
activityInstanceUpdateBufferSizeDetermines the number of updated activity instances that run in a single workflow execution.

Default: 10
activityInstanceUpdateStateBufferSizeDetermines the number of activity instances that have already run and require a state update, such as Status and Completion Date.

Default: 30

Sample code

<sequence.engine>
    ...    <workflowExecution
            activityInstanceUpdateBufferSize="10" 
            activityInstanceUpdateStateBufferSize="30"    
/>

Risks

Depending on how your system uses data, you need to change the default buffer parameters, or configure additional activity properties. 

ConsiderationRecommendation
If your system uses data directly fromtblInstanceActivitiesdatabase table, the database might not have the latest data when required.
Scenarios:  
  • Workflows that include stored procedure activities.
  • Workflows that use the following built-in commands to execute HotOperations actions: Assign and Fetch, Assign, Fetch, and Return.
There are two possible solutions to avoid this issue: 
  • In Cora SeQuence V8.8 and later, set the buffer parameters to "1."
  • In Cora SeQuence V8.8.1 and later, enable the Force Persistence property for the relevant activity.
If an execution fails, the risk of losing data is as big as the configured buffer size.Configure the buffer size carefully based on how your system uses data.