Canakkale 5.2.0
📅 Release Date: January 20, 2026 - 📅 Next Release Date: To Be Announced
Release Summary
Autom Mate Canakkale 5.2.0 is a stability, execution clarity, and operational safety–focused release that strengthens core runtime behavior across Go To flows, error handling, OAuth authentication, monitoring, licensing, and Mate Drive operations.
This release primarily addresses execution-time inconsistencies and visibility gaps that affected complex automation scenarios. Go To behavior inside error handling has been stabilized, logging hierarchies are now consistent, and breadcrumb rendering issues have been resolved. OAuth authentication for Jira and Confluence has been hardened to eliminate refresh token failures observed over time.
In addition, Canakkale 5.2.0 improves version and storage safety through clearer Mate Drive cloning behavior, safer bulk deletion of Autom versions, and stricter license limit enforcement. Monitoring usability and performance have also been enhanced with better sorting, ordering, and reduced redundant backend calls.
Overall, this release focuses on making Autom executions more predictable, traceable, and resilient under real world operational workloads.
Highlights of this Release
🅱️ Bug Fixes
Fixed Jira & Confluence OAuth refresh token failures, ensuring credentials remain usable over time. More Information
Stabilized Go To execution from error handling, eliminating unknown errors and broken transitions.
Resolved breadcrumb and thumbnail rendering issues in runs containing Go To actions.
Corrected Monitoring log hierarchy, ensuring Go To–triggered actions appear as proper child logs.
Fixed misleading license behavior by returning expired license metadata instead of “license not found”.
Resolved tenant custom logo breakage in MSP environments with a stable fallback mechanism.
Fixed credential synchronization and variable detection issues that caused manual rework.
✨ New Features
Automatic Mate Drive cloning when Dev Mode is created for the first time.
Optional Mate Drive clone switch when releasing a version as Active.
Controlled multi version delete option for Autom versions in the frontend.
🛠️ Enhancements
Improved OAuth configuration clarity and usability.
Safer Mate Drive overwrite behavior with explicit confirmation.
Enhanced Monitoring with sorting, clearer ordering, and better log visibility.
Automatic credential synchronization between Vault and Autom flows.
Reduced unnecessary backend calls to improve Flow editor performance.
Introduced login-time license expiration warnings with direct access to License Management.
Preserved product version visibility on the About page even when the license is expired.
Detailed Version
Jira & Confluence Refresh Token Issue
Previously configured Jira and Confluence credentials could become unauthorized after some time, even when the
offline_accessscope was enabled. The OAuth refresh flow has been corrected to ensure refresh tokens are handled reliably and credentials remain usable over time.
Breadcrumb Service Failure with Go To Action
Autom runs containing Go To actions could cause the breadcrumb service to return invalid or incomplete payloads, resulting in broken log rows and missing action thumbnails. Breadcrumb generation and UI rendering are now consistent across Go To and non–Go To runs, with safeguards added for cyclic and edge-case transitions.
Return License Details When License Is Expired
Expired licenses were previously returned as “license not found”, which was misleading and blocked access to license metadata. The service now returns full license details along with an explicit expired status, while preserving existing behavior for active licenses.
MSP Edition: Tenant Custom Logos Breaking Over Time
Tenant custom logos could become inaccessible over time and appear as broken images in MSP environments. A permanent solution has been implemented to stabilize logo access, with a deterministic default avatar shown when a logo cannot be retrieved.
Unknown Error When Go To Calls Main Flow from Error Handling
Invoking main flow actions via Go To from error handling previously resulted in generic “unknown error” responses. This transition has been stabilized so main flow actions can be safely executed, and real failures now return clear, descriptive error messages.
Go To Actions Not Visible as Child Logs
Actions triggered by Go To inside error handling were either missing or displayed as unrelated log entries in Monitoring. Logging behavior has been corrected so Go To entries act as parent logs, with all triggered actions shown as proper child logs.
RWS Authorization Header Override Issue
User-defined
Authorizationheaders in the RWS Action were overridden by Autom Mate’s internal JWT, breaking integrations that required custom authorization. Custom headers are now respected or can be configured explicitly, while maintaining backward compatibility for JWT-based setups.
Multi-layer Variable Location Detection Issue
Multi-layered object and array variables were not correctly detected in the Action Panel. Variable location detection has been fixed, and auto-generated output variables are now consistently visible and correctly mapped.
Vault Credential Updates Not Auto-Syncing
Updating a credential in Vault previously required users to manually reselect the credential in Autom flows. Autom executions now automatically use the latest credential values without user intervention.
Automatic Mate Drive Clone on First Dev Mode Creation
When Dev Mode is created automatically for the first time, Mate Drive content from the Active Version is cloned into the Dev Version. This ensures Dev Mode operates on its own isolated copy and prevents unintended shared writes.
Optional Mate Drive Clone Switch on “Release as Active Version”
A new switch allows users to optionally clone Mate Drive content when releasing a version as Active. The switch is disabled by default and includes warnings about increased storage usage and quota risks.
Multi Version Delete Option
Users can now delete multiple selected Autom versions at once or remove all versions within context. Both actions require confirmation and provide clear success or error feedback in the UI.
OAuth 2.0 Scope Description and Client ID Input Update
OAuth scope descriptions have been clarified to reflect provider-specific formats. The Client ID field is now displayed as a standard text input, while the Client Secret remains securely masked.
Mate Drive Overwrite Support for “Clone to Dev Version”
Cloning to a Dev Version now explicitly overwrites existing Dev Mate Drive content after user confirmation. Confirmation messaging clearly communicates overwrite behavior and potential impact.
Bulk Delete Improvements for Old Autom Versions
Bulk deletion now removes both Autom versions and their associated Mate Drive folders and files, preventing orphaned storage data.
Monitoring Page Service Sorting
Monitoring services can now be sorted by multiple fields, with Created On – DESC applied as the default order.
Monitoring Header Sort Controls
Sort controls have been added to the Monitoring page header, with selections preserved across pagination and navigation.
Prevent Repeated Settings Service Calls in Autom Flow
Redundant settings service calls triggered by minor UI interactions have been eliminated, improving Flow editor performance.
Monitoring Log Summary Order Update
Log summaries are now ordered from newest to oldest, ensuring the most recent errors are always visible at the top.
Autom License Limit Validation and Warning Handling
When active Autom limits are exceeded, the system enters a license violation state and blocks usage until limits are resolved or the license is upgraded.
Tab Usage Preservation for AI Agents
Group action tabs are now preserved during Autom export and import, ensuring tab-based AI agent scenarios remain intact.
Jira & Confluence Connector: Custom Scope Field
A configurable Scope field has been added to Jira and Confluence connectors. User-defined scopes are validated per connection, while
offline_accessis always included automatically.License Expiration Warning on Login (AR-6947)
After a user successfully logs into the platform, an immediate license validity check is performed. If the license is expired, a top-of-UI warning banner is displayed with the message: “Your license has expired on [date]. Please renew to continue using Autom Mate.” The banner clearly shows the expiration date and includes a Renew License button that redirects the user to the in-app License Management page, following existing Autom Mate UI/UX patterns. Once the license is renewed and revalidated, the warning banner is automatically dismissed without requiring any additional user action.
License Expiration – Display Product Version on About Page (AR-6948)
When the license is expired, the About page remains fully accessible, allowing users and support teams to inspect environment details without restriction. The page continues to display the current product version number (for example, Autom Mate Canakkale 5.2.0), retrieved dynamically from the same source used while the license is active. License renewal or upgrade prompts do not block, hide, or obscure version information. The About page maintains the same UI/UX structure and visual consistency in both active and expired license states.
User Notices & Guidance
This section highlights important behavioral changes, usage recommendations, and practical tips introduced in Canakkale 5.1.0. Reviewing these notes will help you adapt existing workflows smoothly and make the most of the new versioning and storage capabilities.
Warnings (Critical Behavior Changes)
Expired licenses are no longer returned as “not found”. Systems that previously relied on a “license not found” response must now handle the expired license state explicitly.
Mate Drive clone operations may overwrite existing Dev content. When using Clone to Dev Version or enabling Mate Drive cloning during release, existing Dev Mate Drive content will be replaced after confirmation.
License violations block system usage. If the number of active Autom flows exceeds the licensed limit, the system enters a blocking license violation state until the limit is resolved.
Bulk version deletion permanently removes Mate Drive data. When deleting Autom versions in bulk, all associated Mate Drive folders and files are removed and cannot be recovered.
Hints (Productivity Tips)
Use Monitoring sort controls to quickly surface the most recent errors by keeping logs ordered from newest to oldest.
Review Mate Drive usage before enabling clone options to avoid unexpected storage growth.
After updating credentials in Vault, no manual re-selection is required. Autom flows will automatically use the latest values.
Best Practices (Recommended Usage)
Perform development and testing activities in Developer versions before releasing changes.
Enable MateDrive cloning only when version isolation is required, and clean up unused Dev data regularly.
Regularly monitor active Autom counts to stay within license limits and avoid execution blocks.
Use bulk delete cautiously and only after confirming that associated Mate Drive data is no longer needed.
Leverage Monitoring sorting and hierarchy features as part of routine operational checks.
Last updated
Was this helpful?