Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property determines whether the MMS API operates in a synchronous or asynchronous mode, affecting how requests are processed and their status tracking. |
| What area does it affect? |
MMS API processing |
| What does the default mean? |
The default value is "false", which means this behavior is disabled by default. |
| When should you review it? |
Review this property when transitioning between synchronous and asynchronous processing modes or troubleshooting request handling. |
Out of the box property record
Raw metadata from the property record.
| Property name |
glide.platform_mm_service.use_sync_flow |
| Sys ID |
cae65932fb22721023daf5b26eefdc1b |
| Type |
boolean |
| Application |
Global |
| Default value |
false |
| Description |
Toggle to use legacy synchronous flow for MMS API. Set to true to use legacy direct processing,
false to use MMS 2.0 async job queue. |
| Updated |
2026-01-23 00:00:00 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... Requests' is expected when the Multimodal Service queue is full. Batch (attachment- driven) submissions are unaffected and continue to report failures correctly. 1. Confirm the asynchronous flow is in use: glide.platform_mm_service.use_sync_flow = false (the default). 2. Make the Multimodal Service return a failure for a direct/on- demand submission. For example, fill the MMS queue, or lower MMS_QUEUE_MAX_DEPTH, so POST /api/v1/jobs answers ...
More in glide.platform_mm_service
Other properties in the same namespace.
All 16 properties in glide.platform_mm_service →