com.glide.cs.va_caching_service.require_lock_to_flushThe property requires a conversation lock to flush cached changes to the sys_cs_conversation database. Admins should be aware of this setting to ensure proper transaction handling and data integrity during worker thread operations.
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This boolean property determines whether a conversation lock is necessary for flushing cached changes to the database at the end of worker thread transactions. |
|---|---|
| What area does it affect? | Conversation caching |
| What does the default mean? | The default value is "true", which means this behavior is enabled by default. |
| When should you review it? | Review this property when configuring conversation handling or troubleshooting data flushing issues. |
Raw metadata from the property record.
| Property name | com.glide.cs.va_caching_service.require_lock_to_flush |
|---|---|
| Sys ID | 35d2eea4ff0032101962ffffffffffb1 |
| Type | boolean |
| Application | Global |
| Default value | true |
| Description | If set to true (the default), a conversation lock is required to flush cached changes to sys_cs_conversation to the DB at the end of cs.worker thread transactions. |
| Updated | 2025-09-14 11:10:40 |