edit

Author: ConnorLand

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/client-activities/synchronize.md

@@ -91,7 +91,7 @@ If you try to trigger another synchronization process while the synchronization
 
 Such an error can be handled in the nanoflow from which the synchronization attempt was triggered using [error handlers](/refguide/error-handling-in-nanoflows/#errorhandlers-nano).
 
-### Background Synchronization
+### Background Synchronization {#background-sync}
 
 Avoid running synchronization processes in the background, such as scheduling periodic refreshes at fixed intervals. This approach can negatively impact application performance and may result in unclear or misleading error messages for users.
 

content/en/docs/releasenotes/studio-pro/10/10.24.md

@@ -22,24 +22,24 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for
 
 ### Fixes
 
-- We fixed an issue that could result in the error "Duplicate objects are not allowed" in the console log when synchronizing offline. But note that the root-cause of this issue is that background synchronization is used, which is not supported in offline apps. (Ticket 235130, 251202)
-- We fixed issue in published OData services where requests that filtered based on associated data combined with 'and' would receive a response containing data that did not match the filter (Ticket 241825).
+- We fixed an issue that could result in the error "Duplicate objects are not allowed" in the console log when synchronizing offline. Please note that the root cause of this issue is the use of background synchronization, which is [not recommended for offline apps](/refguide/synchronize/#background-sync). (Ticket 235130, 251202)
+- We fixed an issue in published OData services where requests that filtered based on associated data combined with 'and' would receive a response containing data that did not match the filter (Ticket 241825).
 - We fixed an issue where retrieving from database in nanoflows failed when using many-to-many associations with XPath constraint going over an association. (Ticket 253996)
 - We fixed an issue where an expression could not be set when the number of available variables was too large, causing the variable list to expand and block access to the expression editor. (Ticket 254957)
-- We fixed an issue where an Oops dialog was displayed when the page variables button was clicked in structure mode for a page template. (Ticket 255394)
-- We fixed an issue where the Combo box widget failed to render when the Store value is configured with a page or snippet variable. (Ticket 256493)
-- Fixed an error where the app would attempt to clear the local cache while developing locally when not running in a secure context (such as localhost). (Ticket 257026)
-- Fixed an issue where doing a hot reload while using the React client would lead the to deployment spinner spinning infinitely in some projects. (Tickets 257026, 257859)
-- We fixed an issue where a foreign key constraint violation in the database could result in a NullPointerException. (Ticket 258430)
-- We fixed an issue where some customers experienced problems logging into their native mobile apps after upgrading to Studio Pro 10.24. The app would enter an authentication loop and return the error: "Could not create a session because the server responded with 401 (Unauthorized)". (Ticket 258696)
+- We fixed an issue where an **Oops** pop-up window was displayed when the page variables button was clicked in structure mode for a page template. (Ticket 255394)
+- We fixed an issue where the combo box widget failed to render when the **Store** value is configured with a page or snippet variable. (Ticket 256493)
+- We fixed an error where apps would attempt to clear their local cache while developing locally when not running in a secure context (such as **localhost**). (Ticket 257026)
+- We fixed an issue where doing a hot reload while using the React client would lead the to deployment spinner spinning infinitely in some projects. (Tickets 257026, 257859)
+- We fixed an issue where a foreign key constraint violation in the database could result in a `NullPointerException`. (Ticket 258430)
+- We fixed an issue where some customers experienced problems logging into their native mobile apps after upgrading to Studio Pro 10.24. The app would enter an authentication loop and return the error: *Could not create a session because the server responded with 401 (Unauthorized)*. (Ticket 258696)
 - We fixed an issue where passing an empty enumeration value to a microflow executed in a task queue would cause the execution to fail. (Ticket 259170)
-- We fixed an issue where datagrid action buttons with empty parameters would cause runtime errors when calling microflows.
-- We fixed an issue for Export Mappings where a user would uncheck a checkbox in the 'Select schema elements' tree structure, but not all children elements were unchecked.
-- We fixed an issue where a "404 - file not found for file: .well-known%2Fappspecific%2Fcom.chrome.devtools.json" error was shown in the Studio Pro console when opening a React app in Chrome with dev tools open. This error was caused by Chrome's automatic workspace folders feature.
-- Fixed an issue with the client parser API where the `groups` option would also require the `places` option.
-- We fixed an issue where previous pages would not load in the React client after closing a page that was opened from a popup.
-- We fixed an issue where a "Manifest: unknown 'display' value ignored" warning was shown in the browser console when opening a non-PWA React app.
-- We fixed an issue where pages with a mix of persistent and non-persistent entity parameters did not load properly on the first time.
+- We fixed an issue where data grid action buttons with empty parameters would cause runtime errors when calling microflows.
+- We fixed an issue for export mappings where a user would clear a checkbox in the 'Select schema elements' tree structure, but not all children elements were deselected.
+- We fixed an issue where a *404 - file not found for file: .well-known%2Fappspecific%2Fcom.chrome.devtools.json* error was shown in the Studio Pro console when opening a React app in Chrome with dev tools open. This error was caused by Chrome's automatic workspace folders feature.
+- We fixed an issue with the client parser API where the `groups` option would also require the `places` option.
+- We fixed an issue where previous pages would not load in the React client after closing a page that was opened from a pop-up window.
+- We fixed an issue where a *Manifest: unknown 'display' value ignored* warning was shown in the browser console when opening a non-PWA React app.
+- We fixed an issue where pages with a mix of persistent and non-persistent entity parameters did not load properly the first time.
 
 ## 10.24.6 {#10246}