You need two settings: “favorites_synchronous_limit” (which is an integer determining if to put the favorite creation on the queue or to do it synchronously) and “favorites_mode” (which is specifying the mode the favorite creation is working in, see below for details)

Response

{
    "favorites_synchronous_limit": 2000,
    "favorites_mode": "existing"
}

Favorites mode documentation

• existing (default): Only uses already existing request, do not create requests otherwise. Asks, if there is more than one request. Non-resolved conflicts will be omitted when generating favorites.
• strict : Always asks on conflict, creates a new request if there is no request. Non-resolved conflicts will always result in new request.
• loose : use existing request or use latest request if there is more than one request. Automatically creates new request otherwise. UI is never shown.
• always : Always asks on conflict, creates a new request if there is no request. Mandatory manual resolution, no automatic generation of requests. Non-resolved conflicts will be omitted when generating favorites.
• never : Never Asks. Uses existing request or creates new one if no request does exist or there is more than one request. UI is never shown.

The workflow works like this: First, all potential conflicts are determined. Then, the product tries to auto-solve the conflicts depending on the set strategy. Afterwards, if there are still conflicts left, the user interface is shown. If the user manually resolves a conflict, the solve method is called with the selected solution. If there is no conflict left, the resolve step is marked as done. Before creating favorites in the backend, a final solve step is done when necessary (this applies e.g. to strict’, where for every unsolved conflict a new request is created automatically, whereas for the ‘existing’ strategy, nothing is done.