Known Issues and Workarounds
Turbine Library:
- Issue #1: When using auto-sync with a remote repository in the Turbine Library, if there’s a conflict between remote and local changes, the merge conflict resolution screen does not appear immediately. Instead, an error is displayed, indicating that publishing to the remote repository has failed.Workaround: Use the manual "Push" option in the Admin panel to trigger the merge conflict resolution screen, allowing you to choose between applying the local or remote changes.
- Issue #2: When publishing content packages to the Library, the publish action fails if the package name contains special characters or duplicates the name of an existing package.Workaround: Ensure that the content package name is unique and does not contain any of the following special characters: /, ?, <, >, , :, *, |, ., .., or ".
- Issue #3: Currently the UI allows user to select the current version of a content package when reverting content to a previous version.Workaround: This is mainly a UI/UX issue and do not impact core functionality. When in this scenario, user will be prompted to enter a new version # and this revert will not result in any changes in the content.
- Issue #4: When user is publishing a custom content package into Turbine Library that may contain previously installed Swimlane content, the “Package Details” dialog may incorrectly display a yellow exclamation icon.Workaround: This is mainly a UI/UX issue and do not impact core functionality. User can disregard the icon and no further action needed.
Remote Agents:
- Known Issue: Remote agents may fail to recover and reconnect after a network disconnection, resulting in repeated “Unexpected error occurred during agent heartbeat” messages.Workaround: A script can be provided to restart the remote agent container. Please contact Support for assistance if you encounter this issue.
Usage Metrics Dashboard
- Issue: In the Events Dashboard, the Triggered Playbooks column is incorrectly showing the number of events instead of the actual count of triggered playbooks.
Turbine Login
- Issue: If an invalid domain name or account name is provided in the settings, any attempts to update will fail without displaying specific error messages.Workaround: Ensure that the domain name is valid before attempting updates. A domain name validity check should be implemented when updates to account settings fail.
Audit Logging
- Issue: The Audit Log API in Swimlane Turbine may encounter a 500 internal server error when attempting to retrieve or display a list of IP addresses in the Source IP field.
Adding Users to Groups
- Issue: When a user is added to a Group the action fails intermittently.Workaround: Add group to user or add group to a role and add to a user.