- Access to the synchronization app is only possible for members of group Administratoren.
- All running synchronization workflows are reported in the corresponding Studio app panel with the very same name.
- Settings for Excluded Properties and Excluded Content Types are only evaluated in Studio frontend while following outgoing references of selected contents, not in the workflow itself.
- Property masterVersion of all content types is ignored during synchronization since it is a more complex task to update it according to user's intention. Localization workflows may thus break or behave unexpectedly due to missing or not updated master versions.
- JWT token for access to the Ingest Service is short-lived and must be renewed every TODO days which implies a change of Studio properties and thus a deployment request. Storing the token in content settings (and making it editable that way) is not recommended for security reasons.
- Finished synchronization workflows cannot be inspected (unlike publication and localization workflows).
- Synchronized contents will always show user workflow as last editor.
- No error messages are shown in Studio UI in case of failure of the synchronization workflow.
- Module iapi-client which serves as the client for a remote Ingest Service does not provide caching of remote contents. A simple caching of remote contents is implemented in the synchronization workflow (which should suffice for typical use cases).