Canakkale 5.1.0
📅 Release Date: December 29, 2025 - 📅 Next Release Date: January 20, 2026
Release Summary
Autom Mate Canakkale 5.1.0 is a maturity and governance-focused release that completes and hardens the versioning foundation introduced in earlier Canakkale updates. While previous releases established multi-version awareness across Autom Mate, this release focuses on making version behavior explicit, enforceable, and operationally safe across MateDrive, Monitoring, Autom execution, and integrations.
A major theme of Canakkale 5.1.0 is predictability. File storage, uploads, deletions, triggers, and executions are now strictly bound to version context, eliminating ambiguity and preventing accidental cross-version impact. MateDrive has evolved into a fully version-isolated storage layer, with per-version quotas, visibility, widgets, and safe operation rules.
From an operational perspective, monitoring and execution flows are now version-aware by default, allowing administrators and technicians to clearly see which version executed what, where files belong, and how storage is consumed. Several long-standing stability issues in gRPC, file handling, dashboards, and messaging integrations have also been resolved, significantly improving reliability under real-world workloads.
With Canakkale 5.1.0, Autom Mate moves from “version-capable” to version-safe by design, ensuring confidence for teams operating complex automation lifecycles.
Highlights of this Release
🅱️ Bug Fixes
⚙️ System & Stability
Resolved UTF-8 gRPC Marshalling Error in XLS Downloads – Fixed a binary encoding issue that caused XLS downloads via RWS GET to fail due to invalid UTF-8 handling.
Stabilized WhatsApp and MS Teams Integrations – Fixed null reference and emoji-related payload parsing errors that caused intermittent trigger failures.
Corrected Dashboard Date Range Calculations – Fixed missing year components in weekly and monthly dashboard filters, ensuring accurate reporting.
Improved File Upload Error Handling – Upload failures now return clear, actionable error messages instead of generic or misleading responses.
Enforced Backend Validation for Cross-Version File Operations – Prevented illegal move or duplicate operations across incompatible versions at the backend level.
Save Attachments Action – Email Trigger Compatibility - Fixed an issue where the Save Attachments action failed when using attachment paths provided by the Email Trigger.
✨ New Features
🗂️ MateDrive Versioning & Storage
Per-Version MateDrive Storage Architecture – Each version now has its own isolated storage space with independent usage tracking and limits.
Version Switching in MateDrive – Users can switch between versions directly within the MateDrive UI to view version-specific files.
Version Information Indicator – A dedicated info button clearly displays the active version context to eliminate ambiguity.
Storage Usage & Limit Widgets – New widgets display total usage, limits, largest files, and recently updated files per version. Mate Drive enforces a file upload limit of 60 MB to maintain system performance.
Folder Management Actions – Added native support for folder creation and controlled deletion behaviors in MateDrive automations.
Redis Namespace Isolation – Implemented version-specific Redis namespaces to prevent data collisions between active and developer environments across runtime and messaging integrations.
🔁 Version Lifecycle Management
Release as Active Version Flow – Developer versions can now be promoted to Active versions through a dedicated release flow.
Version Compare Screen – A full comparison interface allows users to inspect differences between versions before promotion.
Version Limits (Max 100) – Introduced a system-wide cap on the number of versions to maintain performance and governance.
Strict Preview Enforcement for Active & Old Versions – Active and Old versions are now read-only by design.
Dev Mode Visibility Enhancements – When Dev Mode is enabled, the related Developer version is clearly surfaced.
Explicit &dev Indicators for APIs and Webhooks – Developer version endpoints are now clearly marked to prevent accidental production usage.
Trigger Rules per Version State – Triggers now behave differently based on whether a version is Developer or Published.
🛠️ Enhancements
📊 Monitoring & Operations
Version-Aware Monitoring Screens – Monitoring views now include version columns, search, and advanced filtering.
Autom Execution Version Tracking – Every operation now records which Autom version was executed, improving auditability.
Improved Action Detail Views in Version Compare – Action-level differences are displayed more clearly during comparisons.
🧠 User Experience & Usability
Improved MateDrive Navigation – Folder trees, breadcrumbs, and path-aware actions significantly improve navigation in deep structures.
Consistent File Listings – Fixed duplicate listing issues when uploading identical files.
Persistent Groupable Tabs in Autom Editor – Grouped tabs now retain their open/closed state between sessions.
Detailed Version
⚙️ System & Stability
Resolved UTF-8 gRPC Marshalling Error in XLS Downloads When downloading XLS files via RWS GET, the system encountered gRPC marshalling failures caused by invalid UTF-8 interpretation of binary content. This issue resulted in failed downloads or corrupted files, especially for larger exports. The root cause was identified as improper encoding handling during response serialization. The download pipeline has been updated to treat XLS content as binary-safe data. Encoding validation was corrected to prevent UTF-8 assumptions on non-text payloads. As a result, XLS downloads are now stable and reliable. This fix improves data export consistency across all RWS consumers.
Stabilized WhatsApp and MS Teams Integrations Intermittent failures were observed in WhatsApp and Microsoft Teams triggers due to null reference scenarios and emoji characters in incoming payloads. These issues caused triggers to fail silently or stop processing altogether. Payload validation and parsing logic have been hardened to safely handle optional fields and special characters. Emoji support is now fully compatible with downstream processing. Additional null checks were introduced to prevent unexpected runtime errors. Integration stability has significantly improved under real-world message loads. Trigger execution is now predictable and resilient.
Corrected Dashboard Date Range Calculations Dashboard filters for weekly and monthly views produced incorrect results due to missing year components in date range calculations. This caused reports to include partial or unintended time periods. The date calculation logic has been corrected to always include explicit year boundaries. Filter behavior is now consistent across different calendar transitions. Historical and current period reports now align with user expectations. This fix ensures accurate analytics and trend analysis. Reporting reliability has been improved for all dashboard users.
Improved File Upload Error Handling File upload failures previously returned generic or misleading error messages, making troubleshooting difficult for users. In some cases, the actual cause of the failure was hidden or unclear. Error handling logic has been revised to surface precise and actionable messages. Validation errors, size limits, and permission issues are now clearly distinguished. Users can immediately understand why an upload failed and how to resolve it. This reduces unnecessary retries and support requests. Overall upload usability and transparency have been improved.
Enforced Backend Validation for Cross-Version File Operations Certain edge cases allowed file move or duplicate operations to bypass version boundaries at the backend level. This created a risk of files being unintentionally shared or modified across incompatible versions. Additional backend validation rules have been implemented to strictly enforce version isolation. All file operations are now validated against their source and target version contexts. Invalid cross-version requests are rejected consistently, regardless of UI behavior. This guarantees data integrity across version lifecycles. Version safety is now enforced by design rather than convention.
Save Attachments Action – Email Trigger Integration An issue related to the Save Attachments action when used with the Email Trigger has been resolved. Previously, using a static path value could result in a path not found error during execution. Additionally, dynamic path values coming from email trigger variables could fail due to invalid character parsing. The attachment path handling logic has been improved to properly validate and process both static and trigger-based inputs. This ensures stable and reliable attachment saving in email-driven automation scenarios.
🗂️ MateDrive Versioning & Storage
Per-Version MateDrive Storage Architecture MateDrive storage has been restructured to operate on a strict per-version basis. Each version now maintains its own isolated storage space with independent usage calculation and quota enforcement. This change eliminates the risk of one version consuming storage allocated to another. Storage metrics are now accurately tracked at the version level. The new architecture provides predictable storage behavior across Dev, Active, and Old versions. It also lays the groundwork for version-aware storage analytics. Overall data isolation and governance are significantly improved.
Version Switching in MateDrive A dedicated version-switching capability has been added directly to the MateDrive interface. Users can now switch between versions without leaving the screen or relying on indirect navigation. This enables quick inspection of files belonging to different versions. The switch action immediately refreshes file listings to reflect the selected version context. Visual feedback ensures users are always aware of the active version. This reduces operational friction when working with multi-version environments. File management across versions is now more intuitive and controlled.
Version Information Indicator A version information indicator has been introduced to clearly display the current version context. This indicator removes ambiguity when performing file-related operations. Users can instantly verify whether they are operating in a Developer, Active, or Old version. The indicator is consistently visible across relevant MateDrive views. This prevents accidental actions in protected versions. Version awareness is now explicit rather than implicit. The overall user confidence during file operations is improved.
Storage Usage and Limit Widgets New widgets have been added to visualize storage usage and limits at the version level. These widgets display total usage, remaining capacity, and version-specific consumption patterns. Users can quickly identify storage-heavy versions without manual inspection. The widgets update dynamically as files change. This visibility supports proactive storage management before promotion or release. It also helps detect abnormal growth early. Storage monitoring is now integrated directly into the MateDrive experience. Mate Drive enforces a file upload limit of 60 MB to maintain system performance.
Largest and Recently Updated Files Widgets MateDrive now includes widgets for the largest files and the most recently updated files. These widgets provide file name, size, and path information for faster analysis. Users can quickly identify files that may impact storage limits or require review. Recently updated files help track active changes within a version. This improves transparency during development and validation phases. File insights are available without navigating deep folder structures. Operational awareness is significantly enhanced.
Folder Management Actions in MateDrive New folder management capabilities have been introduced within the MateDrive action library. Users can now create folders programmatically as part of automation flows. File deletion behavior has also been enhanced with explicit delete-type control. These actions provide greater flexibility when managing structured file systems. Folder operations are fully version-aware and respect version boundaries. This enables more advanced file orchestration scenarios. MateDrive automation capabilities are expanded significantly.
Redis Namespace Isolation for Versioned Runtime Version-specific Redis isolation has been introduced to ensure strict separation between active and developer environments. The matedb runtime cache now operates within dedicated Redis namespaces or database indexes per version type. WhatsApp, WhatsApp 360, and Microsoft Teams integrations also persist their runtime and session data in version-aware Redis areas. This approach prevents developer testing from impacting active production pipelines. Existing active version behavior remains unchanged and fully backward compatible.
🔁 Version Lifecycle Management
Release as Active Version Flow A dedicated flow has been introduced to promote Developer versions to Active versions. This formalizes the release process and reduces manual steps. Users can now clearly initiate a release action with predictable results. The flow ensures version metadata is updated consistently. This reduces errors during promotion. Release operations are now easier to understand and execute. Version lifecycle management becomes more structured and reliable.
Version Compare Screen A new Version Compare screen allows users to compare differences between versions before promotion. The screen highlights structural and action-level changes clearly. This enables informed release decisions and reduces regression risk. Users can validate changes without manually inspecting configurations. The comparison experience is designed for clarity and accuracy. It supports safer transitions from Dev to Active. Change visibility across versions is greatly improved.
Version Limit Control (Max 100 Versions) A system-wide version limit of 100 has been introduced to maintain performance and manageability. This prevents uncontrolled version proliferation over time. Users are informed when the limit is reached. The system enforces the limit consistently across all creation flows. This ensures long-term stability in large environments. Version governance is now explicit rather than advisory. Operational predictability is improved.
Strict Preview Enforcement for Active and Old Versions Active and Old versions are now strictly enforced as preview-only environments. Editing and destructive operations are fully disabled by design. This prevents accidental modification of production or historical versions. Users can safely inspect content without risk. All changes must be performed in Developer versions. This establishes a clear and enforceable lifecycle model. Version safety is significantly strengthened.
Dev Mode Visibility Enhancements When Dev Mode is enabled, the related Developer version is now clearly surfaced even when viewing Active or Old versions. This helps users understand the relationship between released and in-progress work. Context switching becomes more transparent. Users can quickly identify where active development is happening. This reduces confusion in multi-version environments. Dev Mode behavior is now explicit and predictable. Development workflows are easier to follow.
Explicit &dev Indicators for APIs and Webhooks API and Webhook URLs now automatically include a
&devindicator when associated with Developer versions. This clearly distinguishes development traffic from production usage. It reduces the risk of unintentionally calling production endpoints during testing. Endpoint behavior is now self-descriptive. This improves safety during integration development. Debugging and validation become easier. Version-aware integrations are now more reliable.
Trigger Rules per Version State Trigger execution behavior has been separated based on version state. Developer and Published versions now follow different trigger management rules. This ensures triggers behave consistently with the version lifecycle. Unintended executions in production are prevented. Trigger logic is now aligned with version intent. Automation behavior becomes more predictable. Operational control is significantly improved.
📊 Monitoring & Operations
Version-Aware Monitoring Screens Monitoring screens have been enhanced to fully support version awareness across all operational views. Version information is now displayed directly within monitoring lists, allowing users to immediately identify which version generated an event or execution. Advanced filtering and search capabilities have been extended to include version criteria. This improves troubleshooting accuracy in multi-version environments. Users can isolate issues without cross-referencing external data. Operational visibility is now aligned with version governance. Incident analysis becomes faster and more reliable.
Autom Execution Version Tracking Each operation now records the exact Autom version that was executed. This enhancement improves traceability across logs, monitoring, and audit workflows. Users can correlate execution results with the corresponding version state. This is particularly valuable when comparing behavior across releases. Historical analysis is now more accurate and actionable. The enhancement strengthens compliance and audit readiness. Operational accountability is significantly improved.
Improved Action Detail Views in Version Compare Action-level details in the Version Compare screen have been refined for clarity. Differences between actions are now presented in a more structured and readable format. This reduces cognitive load when reviewing complex changes. Users can quickly identify what has been added, removed, or modified. The improved view supports safer release decisions. Comparison workflows are more efficient. Change validation is now more intuitive.
🧠 User Experience & Usability
Improved MateDrive Navigation MateDrive navigation has been enhanced with folder trees, breadcrumbs, and path-aware interactions. Users can now move through deep folder structures with ease. File locations are always visible and understandable. This reduces navigation errors and repetitive clicks. The experience is consistent across different versions. File management workflows are smoother and faster. Overall usability is significantly improved.
Consistent File Listing Behavior File listing behavior has been optimized to ensure consistent and predictable results. Duplicate entries caused by repeated uploads have been eliminated. File identity and path resolution are now handled more reliably. Users can trust the accuracy of file lists. This reduces confusion during validation and review processes. File visibility is aligned with version context. The MateDrive experience is now more deterministic.
Persistent Groupable Tabs in Autom Editor Groupable tabs in the Autom editor now retain their open or closed state across sessions. Users can resume work without reconfiguring their workspace. This improves continuity during long or complex automation design tasks. The editor feels more responsive to user preferences. Cognitive overhead is reduced. Productivity increases over extended editing sessions. The enhancement improves overall editor usability.
🌐 Integrations & Libraries
Zendesk Application Library Integration Zendesk has been added as a native application within the Autom Mate Application Library. Users can now leverage Zendesk actions and triggers without custom integration work. This simplifies automation design for customer support workflows. Integration consistency is improved through standardized connectors. Configuration effort is reduced. Automation coverage expands to new use cases. The platform becomes more versatile.
JIRA Credential Configuration Simplification The deprecated API Token credential option has been removed from the JIRA frontend configuration. This reduces confusion and prevents incorrect credential selection. Users are now guided toward supported and secure authentication methods. Misconfiguration risks are minimized. The setup experience is clearer and more streamlined. Integration reliability improves as a result. Credential management becomes simpler and safer.
Mate Agent Synchronization with MateDrive MateDrive now automatically refreshes when an Autom’s assigned Mate Agent changes. This ensures file context remains consistent with execution environment changes. Users no longer need to manually refresh or reconcile state mismatches. Synchronization is handled transparently in the background. This prevents stale or misleading file views. Operational confidence is increased. Agent changes are now fully reflected in storage behavior.
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)
Active and Old versions are now read-only. Upload, move, delete, or edit operations are not allowed in these versions.
All file changes must be done in Developer versions. This protects production and historical environments.
Cross-version file operations are blocked. Files cannot be moved or duplicated between incompatible versions.
Mate Drive storage is isolated per version. Storage usage in one version does not affect others.
Developer APIs and Webhooks include a
&devindicator. Endpoints should be carefully verified before production use.A maximum of 100 versions is enforced per environment. New versions cannot be created once the limit is reached.
Hints (Productivity Tips)
Check the Version Info indicator before performing file or automation actions.
Use the Version Compare screen to review changes before releasing.
Apply version filters in Monitoring to narrow down operational issues.
Keep Developer versions clean by removing temporary or test files.
Monitor storage widgets to detect large or fast-growing files early.
Use folders and breadcrumbs to navigate complex MateDrive structures.
Adopt clear and consistent version naming conventions.
Best Practices (Recommended Usage)
Perform development and file changes only in Developer versions.
Promote changes using the Release as Active Version flow.
Treat Active versions as production snapshots that should not be modified.
Use Old versions only for reference or audit purposes.
Always validate API and Webhook endpoints before connecting external systems.
Review per-version storage usage regularly.
Retire unused versions to stay within the version limit.
Last updated
Was this helpful?