Microsoft Teams v2.0.1 SyncPack is Released
Hello, We are pleased to announce the release of Microsoft Teams v2.0.1 SyncPack. The following issue was addressed in this release: Addressed an issue that prevented configuration objects from being visible after installing the SyncPack. (Case: 00559847) Thank you, Release Management7Views1like0CommentsSkylar Compliance Automation PowerPack v105
Hello, We are pleased to announce the release of Skylar Compliance Automation PowerPack v105. The following issues were addressed in this release: With this release, ScienceLogic has rebranded the "Restorepoint Automation" PowerPack to the "Skylar Compliance Automation" PowerPack. This change, as well as similar branding changes to the other products offered by ScienceLogic, reflects ScienceLogic's commitment to delivering intelligence that accelerates outcomes through service-centric observability, AI-driven operations, and intelligent automation. For more information, see the ScienceLogic website (https://sciencelogic.com/platform/overview). Resolved an indentation error that caused the "Restorepoint: Generic Action type" snippet to fail when executing the "Start Restorepoint Backup" Run Book automation policy. (Case: 00534255) Thank you, Release Management3Views0likes0CommentsServiceNow Incidents SyncPack v4.2.1 is Released
Hello, We are pleased to announce the release of ServiceNow Incidents SyncPack v4.2.1. Version 4.2.1 of the ServiceNow Incidents SyncPack updates the "Lock" feature to use a Redis lock instead of a Couchbase lock, which allows the SyncPack to function correctly when using DynamoDB or Couchbase as a database. You can download this update from the Support Center page. NOTE: This SyncPack uses the "ServiceNow Base Pack" PowerPack. Thank you, Release Management10Views1like0CommentsSkylar Automation System Utils v1.3.0 SyncPack is Released
Hello, We are pleased to announce the release of Skylar Automation System Utils v1.3.0 SyncPack, which is now available on the portal: https://support.sciencelogic.com/s/release-file/aBtVL0000001CaD0AU/skylar-automation-system-utils-synchronization To use this SyncPack, you must install Base Steps SyncPack. Thank you, Release Management21Views0likes0CommentsSkylar Automation v3.3.0 and Skyautoctl v2.9.0 are Released
Hello, We are pleased to announce the release of Skylar Automation platform v3.3.0 and the Skylar Automation skyautoctl Command Line Utility v2.9.0. You can download these releases from here: https://support.sciencelogic.com/s/release-version/aBuVL00000019Vt0AI/skylar-automation-33 Skylar Automation (formerly PowerFlow) version 3.3.0 rebrands PowerFlow to Skylar Automation, rebrands powerflowcontrol (pfctl) to skyautocontrol, updates the user interface of the SyncPacks page, and addresses multiple issues. Features PowerFlow is now Skylar Automation. With this release, ScienceLogic has rebranded PowerFlow to Skylar Automation. You will notice this rebranding throughout the platform. This change, as well as similar branding changes to the other products offered by ScienceLogic, reflects ScienceLogic's commitment to delivering intelligence that accelerates outcomes through service-centric observability, AI-driven operations, and intelligent automation. For more information, see the ScienceLogic website (https://sciencelogic.com/platform/overview). The powerflowcontrol (pfctl) command-line utility has been rebranded to skyautocontrol (skyautoctl) as part of the rebrand from PowerFlow to Skylar Automation. All of the older pfctl and iservicecontrol commands still function. Updated the user interface of the SyncPacks page in Skylar Automation to improve clarity around the installed version of SyncPacks: Updated the Active Version column to Installed Version Updated the Change Active Version option in the Actions menu to Change Installed Version Skylar Automation v3.3.0 includes package updates to improve security and system performance. Among other things, these updates address critical vulnerability CVE-2025-49844. Updated Skylar Automation to prevent search engines from indexing Skylar Automation systems by default, improving system privacy and reducing the risk of external exposure. Updated the Redis service to Redis 7.4.6. The following images are included in this release of Skylar Automation: registry.scilo.tools/sciencelogic/sa-api:rhel3.3.0 registry.scilo.tools/sciencelogic/sa-couchbase:6.6.0-15 registry.scilo.tools/sciencelogic/sa-dex:2.37.1-12 egistry.scilo.tools/sciencelogic/sa-worker:rhel3.3.0 registry.scilo.tools/sciencelogic/sa-gui:3.3.0 registry.scilo.tools/sciencelogic/sa-pypi:6.3.1-16 registry.scilo.tools/sciencelogic/sa-rabbit:3.8.35-8 registry.scilo.tools/sciencelogic/sa-redis:7.4.6-0 Issues Addressed The following issues were addressed in this release: Improved stability when using the broker_load_from_backend feature. Skylar Automation steprunner services now handle missing task bodies in Redis more effectively. If a task's payload has been evicted from Redis, the worker will mark the task as failed instead of hanging. This keeps the worker healthy and allows other tasks in the queue to process normally. (Cases: 00554106, 00554534) In some Dex OIDC connector configurations used for Skylar Automation authentication, the email claim may not be provided. Previously, this caused endpoints that relied on the current user identity to fail, showing 500 errors. Now, when the email is missing, Skylar Automation uses the username to identify the user. This ensures widgets, favorites, and related features work correctly by consistently associating data with the authenticated user, even when the email claim is unavailable. (Case: 00524073) Updated the Skylar Automation backup application to clean up the staging directories inside the steprunner containers and to ensure that if the backup fails to copy to a remote system, the temporary files do not hang in the system. (Case: 00513115) Improved error handling to provide more information about why the graphical user interface is not displaying the SystemHealth diagram after logging into Skylar Automation. (Case: 00467441) Addressed an issue that prevented the "Timed Removal" application from running. Thank you, Release Management17Views0likes0Comments