In version 24, the following call seems to show up very often in the REST log:
20250929/145458.776 - 49 U00045098 Method 'GET', URL: 'https://rest-endpoint.example.com:8443/ae/api/v1/100/system/settings/UC_SENDTO', received from IP: '##.##.#.#' 'User: AUTOMIC/AUTOMIC'
20250929/145458.776 - 58 U00045098 Method 'GET', URL: 'https://rest-endpoint.example.com:8443/ae/api/v1/100/system/settings/UC_SENDTO', received from IP: '##.##.#.#' 'User: AUTOMIC/AUTOMIC'
20250929/145458.777 - 54 U00045098 Method 'GET', URL: 'https://rest-endpoint.example.com:8443/ae/api/v1/100/system/settings/UC_SENDTO', received from IP: '##.##.#.#' 'User: AUTOMIC/AUTOMIC'
20250929/145458.780 - 58 U00045099 The server replied with following status: '200' SessionId: '4761017'
20250929/145458.780 - 49 U00045099 The server replied with following status: '200' SessionId: '4761017'
20250929/145458.784 - 54 U00045099 The server replied with following status: '200' SessionId: '4761017'
Why is this?
Version: 24+
This is as designed. The design of the product is moving certain routines away from direct database queries to REST calls instead and this is a more efficient way to do this. Right-clicking objects has always run a check against the database for what should be shown in the "Send To" menu. Now it's moving towards REST.