# Canakkale 5.5.0 ## Release Summary Autom Mate **Canakkale 5.5.0** introduces a redesigned **Monitoring architecture and log lifecycle management system**, along with a new **sidebar experience** and platform-wide performance improvements. This release fundamentally changes how operation logs are stored, accessed, and visualized. Monitoring now distinguishes between **Live, Archive, and All log sources**, enabling clearer separation between recent and historical executions. A new retention-based lifecycle ensures that operations transition automatically from live visibility to archived storage, improving performance and scalability. In addition, Canakkale 5.5.0 introduces a **new sidebar design** with improved navigation structure, while preserving access to the previous layout through personalization settings. Performance optimizations have also been applied across the platform to improve responsiveness in high-volume environments. Overall, this release focuses on improving **observability, system performance, and user navigation experience** through structural improvements in Monitoring and UI design. *** ## **Highlights of this Release** ### 🅱️ **Bug Fixes** * Fixed inconsistencies in Monitoring log visibility across different execution states. * Fixed issues related to operation log access after lifecycle transitions. * Fixed UI inconsistencies in navigation components during layout updates. *** ### ✨ **New Features** * Introduced **new sidebar design** for improved navigation experience. * Added **log source filtering in Monitoring** (Live / Archive / All). * Introduced **operation log lifecycle management system**. * Added **automatic archiving mechanism** for operations after 14 days. * Introduced **archive-based log browsing under Monitoring**. * Added **log retention configuration for on-prem environments**. *** ### 🛠️ **Enhancements** * Improved Monitoring performance through log separation and lifecycle handling. * Optimized operation log storage and retrieval mechanisms. * Enhanced scalability for high-volume operation environments. * Improved overall system performance across core modules. *** ## **Detailed Version** {% tabs %} {% tab title="🅱️ Bug Fix" %} * #### Monitoring Log Visibility Inconsistencies Operation logs could appear inconsistently across different Monitoring views depending on execution timing and system state. Log visibility behavior has been stabilized to ensure consistent display across all Monitoring views. *** * #### Operation Log Access After Lifecycle Transition In some scenarios, logs transitioning between states could become temporarily inaccessible. Lifecycle handling has been corrected to ensure logs remain accessible during and after transitions. *** * #### Sidebar UI Inconsistencies During layout updates, certain sidebar elements could render inconsistently. UI rendering behavior has been corrected to ensure stable sidebar presentation. {% endtab %} {% tab title="✨ New Features" %} * #### New Sidebar Design A new sidebar structure has been introduced to improve navigation clarity and accessibility across the platform. The updated design provides a more structured layout for accessing core modules and features. *** * #### Legacy Sidebar Access via Personalization The previous sidebar layout is now accessible through the **Personalization** section in Settings. This allows users to switch between the new and legacy navigation experience. *** * #### Monitoring Log Source Filtering (Live / Archive / All) Monitoring now includes a **log source selector** with three modes: * **Live:** Displays recent operations * **Archive:** Displays archived operations * **All:** Displays all operations This enables more efficient filtering and analysis of execution history.. *** * #### Operation Log Lifecycle Management A new lifecycle model has been introduced for operation logs. Operations are now managed based on age and automatically transition between live and archived states. *** * #### Automatic Archiving After 14 Days Operations are classified as **Live** for the first 14 days. After this period, operations are automatically moved to the **Archive** state. *** * #### Archive View for Historical Operations Archived operations are accessible under the **Archive** view in Monitoring. This provides a clear separation between active and historical execution data. *** * #### Log Retention Configuration (On-Prem Only) On-prem environments can configure log retention duration through the **Log Retention settings screen**. Available retention options: * 6, 12, 24, 36, 48, 60 months {% endtab %} {% tab title="🛠️ Enhancements" %} * #### Monitoring Performance Improvements Monitoring performance has been improved through separation of live and archived data sources. This reduces load on active queries and improves responsiveness. *** * #### Optimized Log Storage and Retrieval Operation log storage mechanisms have been optimized to support large-scale environments. Retrieval performance has been improved for both live and archived logs. *** * #### Scalable Log Lifecycle Handling The new lifecycle model improves scalability by reducing the amount of actively processed data. Archived logs are handled separately to optimize system performance. *** * #### System-Wide Performance Improvements General performance optimizations have been applied across the platform to improve responsiveness and execution efficiency. {% endtab %} {% endtabs %} *** ## User Notices & Guidance This section highlights important behavioral changes and system-level updates introduced in Canakkale 5.5.0. {% hint style="danger" %} #### Warnings (Critical Behavior Changes) * **Log Lifecycle Behavior Change**\ Operations are now automatically archived after 14 days.\ Users should use the **Archive** or **All** views to access older executions. * **Cloud Log Retention Policy**\ In cloud environments, log retention is fixed at **6 months** and cannot be modified.\ After this period, operations and logs are permanently deleted. * **On-Prem Log Retention Configuration**\ On-prem environments can configure retention duration via settings.\ After the configured retention period, logs are permanently deleted. * **Monitoring Data Separation**\ Live and archived logs are now handled separately.\ Users should select the correct log source when searching for executions. {% endhint %} *** {% hint style="info" %} #### Hints (Productivity Tips) * Use the **Live view** to focus on recent executions (last 14 days). * Use the **Archive view** to analyze historical execution data. * Use the **All view** when full execution history is required. * Switch to the **legacy sidebar** from Personalization if needed during transition. {% endhint %} *** {% hint style="success" %} #### Best Practices (Recommended Usage) * Use Live Monitoring for active debugging and recent executions. * Use Archive view for historical analysis and audit scenarios. * Configure retention settings appropriately in on-prem environments based on storage policies. * Regularly review log usage to ensure optimal system performance. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.autommate.com/userguide/release-notes/canakkale-edition/canakkale-5.5.0.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.