Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Canakkale 5.6.0

Historical release note. This page describes this version at its release; use the Dublin notes and current guides for the latest product behavior.

Release Summary

Autom Mate Canakkale 5.6.0 introduces improvements across MateDrive performance, Hyper Flow execution visibility, product terminology, gateway stability, authentication capabilities, and workflow control.

This release includes a new low-resource MateDrive upload service designed to reduce RAM and CPU usage during large file operations. MateDrive download stability has also been improved to prevent Gateway Timeout errors and protect environment accessibility during large file downloads.

Canakkale 5.6.0 also expands workflow capabilities with response header support in the Stop action, multipart/form-data trigger parsing, OAuth client credentials support with Basic Auth Header, a new Array library merge action, and a version-aware rerun mechanism for failed operations.

In addition to these new capabilities, this release includes product-wide UI and terminology updates, including the transition from “Automs” to “Hyper Flow,” updated navigation naming, descriptive page texts, and modernization of legacy management pages.

Several stability issues have also been resolved, including backend crashes during high-volume log searches, gateway service crashes caused by rate limiter behavior, Elasticsearch retry continuation after Summary screen closure, incorrect elapsed time in Monitoring, and internal MateDrive delete action errors.

Overall, Canakkale 5.6.0 strengthens platform stability, improves performance in high-volume scenarios, and continues the product-wide transition toward a clearer, more consistent automation experience.

Highlights of this Release

🅱️ Bug Fixes

  • Fixed Gateway Timeout and environment access issues after downloading large files from MateDrive.

  • Fixed missing Else condition steps in logs and empty Logs Summary screens.

  • Fixed Elasticsearch retry processes continuing after the Summary screen is closed.

  • Fixed gateway service crash caused by nil pointer dereference in AdjustRateLimiter.

  • Fixed MateDrive Delete action exposing internal errors when file name is null.

  • Fixed backend crash during log searches with multiple filters and high data volume.

  • Fixed errors when switching variable types to Date from other formats.

  • Fixed incorrect total elapsed time display in Monitoring.

✨ New Features

  • Low-resource MateDrive upload service.

  • Response Header support in Stop action.

  • Multipart/form-data trigger payload parsing.

  • OAuth client credentials Basic Auth Header support for App Library authentication.

  • New Array library action for merging two arrays.

  • Failed operation rerun mechanism with version selection and operation linking.

🛠️ Enhancements

  • Legacy management pages updated with the new design system.

  • Product-wide terminology and navigation naming updates.

  • Product page descriptive texts added.

  • “Automs” terminology replaced with “Hyper Flow” across the product.

  • Gateway project RAM and CPU performance optimizations.

  • Library version list performance improvements.

Detailed Version

  • MateDrive Large File Download Gateway Timeout Issue

    Downloading large files from MateDrive could cause Gateway Timeout errors and make the environment temporarily inaccessible.

    Large file download handling has been improved to preserve platform availability, reduce timeout risk, and provide safer behavior during file transfer failures.

  • Else Condition Missing from Logs

    When a workflow executed an Else branch and later failed, the Else condition step was not always displayed in the logs.

    Executed Else condition branches are now shown correctly in the log list, helping users understand which path was followed during troubleshooting.

  • Empty Logs Summary Screen for Failed Operations

    The Logs Summary screen could appear empty for failed operations even when execution steps were available.

    Logs Summary behavior has been corrected so executed steps remain visible and failure analysis can be performed accurately.

  • Elasticsearch Retry Continues After Summary Screen Closure

    The Summary screen retry mechanism for Elasticsearch continued running even after the user closed the screen or navigated away.

    Retry lifecycle handling has been updated so retry processes are cancelled when the Summary screen is closed, preventing unnecessary background requests and resource usage.

  • Gateway Rate Limiter Nil Pointer Crash

    The gRPC gateway service could crash with a SIGSEGV error due to nil memory information handling in the AdjustRateLimiter function.

    Nil checks and safer locking behavior have been added to prevent gateway crashes and improve service stability in ECS/Docker environments.

  • MateDrive Delete Action Internal Error Exposure

    The MateDrive Delete action could expose internal stack traces and source references when the file name was null or empty.

    Validation has been added so missing file names now return a clear user-friendly error instead of exposing internal technical details.

  • Backend Crash During High-Volume Log Search

    The backend could crash when users searched large log datasets using the top search bar together with multiple filters.

    Log search handling has been optimized to prevent crashes and improve stability when filtering high-volume log data.

  • Variable Type Change to Date Error

    Changing a variable from another format, such as Array, to Date could cause errors because the default value was not handled properly.

    Variable type switching behavior has been improved to handle Date conversion scenarios more safely.

  • Incorrect Total Elapsed Time in Monitoring

    Monitoring could show an incorrect total elapsed time in summary information, even though the internal Autom end time data was correct.

    Elapsed time calculation and display behavior have been corrected to ensure Monitoring shows accurate execution duration.

  • Low-Resource MateDrive Upload Service

    A new MateDrive upload service has been introduced to reduce resource consumption during file upload operations.

    The service is designed to use streaming or chunk-based processing, preventing large files from being fully loaded into memory and improving stability during large uploads.

  • Stop Action Response Header Support

    The Stop action now supports a new Response Header section.

    Users can define response headers in key-value format for API-triggered Hyper Flow executions, allowing custom headers to be returned together with response body, status code, and response type.

  • Multipart/Form-Data Trigger Payload Parsing

    Autom Mate can now parse multipart/form-data trigger requests into usable trigger data.

    Form fields and file metadata can now be converted into structured trigger data and used as variables inside workflows.

  • App Library OAuth Basic Auth Header Support

    App Library authentication now supports OAuth client_credentials flows where client authentication is sent through the Basic Auth Header.

    This enables integrations such as Fiserv to retrieve access tokens using Authorization: Basic header authentication while preserving existing authentication methods.

  • Array Library Merge Arrays Action

    A new Array library action has been added to merge two arrays into a single output array.

    The action accepts two array inputs, preserves order, and returns a combined array output for use in Hyper Flow workflows.

  • Failed Operation Rerun Mechanism

    A new rerun mechanism has been introduced for failed operations.

    Users can rerun eligible failed operations by selecting either the Active version or Dev version. Each rerun creates a new linked operation, keeping the original operation traceable in Monitoring.

  • New Design System for Legacy Management Pages

    Legacy management pages have been updated to align with the current Autom Mate design system.

    The updated pages include Alerts, Queue, Custom Credentials, and Webhook API, improving UI consistency while preserving existing functionality.

  • Product-Wide Terminology and Navigation Naming Updates

    Module, menu, and screen names have been reviewed and updated to better align with the current product language.

    This includes terminology improvements for Libraries, Apps, Market-related navigation, and Dashboard Summary Mail placement and naming.

  • Product Page Descriptive Texts

    Descriptive texts have been added to product pages to help users understand the purpose and usage of each module.

    These descriptions improve onboarding, module discoverability, and overall user guidance across the platform.

  • “Automs” Renamed to “Hyper Flow”

    The term “Automs” has been replaced with “Hyper Flow” across the product.

    This update applies to sidebar navigation, creation modals, page titles, breadcrumbs, buttons, empty states, help texts, notifications, and related UI components.

  • Monitoring Terminology Update

    Monitoring references such as “Autom History” have been updated to “Execution History.”

    This change supports the broader Hyper Flow terminology transition and improves clarity in execution-related screens.

  • Gateway Performance and Resource Optimization

    Gateway project performance has been improved through RAM and CPU optimization.

    The optimization focuses on setVariable flow behavior, Object and Array library operations, repetitive execution paths, and high-volume workload stability.

  • Library Version List Performance Improvement

    The library version list screen has been optimized to reduce excessive data loading.

    Data fetching behavior has been improved through better listing strategy, reduced unnecessary transfer, and support for more stable performance in large dataset scenarios.

User Notices & Guidance

This section highlights important behavioral changes, usage recommendations, and practical tips introduced in Canakkale 5.6.0. Reviewing these notes will help users adapt existing workflows smoothly and make the most of the new Hyper Flow terminology, MateDrive improvements, rerun capabilities, and authentication updates.

Warnings (Critical Behavior Changes)

  • Product Terminology Update “Automs” has been renamed to “Hyper Flow” across the product. Users should expect updated naming in menus, screens, buttons, breadcrumbs, help texts, and Monitoring-related areas.

  • Monitoring History Naming Change “Autom History” and similar Monitoring references have been updated to “Execution History.”

  • MateDrive Validation Behavior MateDrive Delete actions now return validation errors when required fields such as file name are missing. Internal technical errors are no longer exposed in the UI.

  • Summary Screen Retry Lifecycle Elasticsearch retry behavior is now tied to the Summary screen lifecycle. Closing the screen cancels ongoing retry attempts.

  • Rerun Operation Restrictions Only original eligible operations can be rerun. Operations created through rerun cannot be rerun again.

Hints (Productivity Tips)

  • Use Response Header support in the Stop action when API-triggered Hyper Flows need to return custom headers to external systems.

  • Use multipart/form-data trigger parsing when receiving form submissions or file-related trigger payloads.

  • Use the new Merge Arrays action when combining two array outputs inside a Hyper Flow.

  • Use the rerun mechanism to re-execute failed operations with either the Active version or Dev version while preserving traceability.

  • Use Basic Auth Header authentication in App Library OAuth settings when integrating systems that require client_id and client_secret in the Authorization header.

  • Review updated product page descriptions to better understand module purpose and usage.

Best Practices (Recommended Usage)

  • Validate large MateDrive upload and download workflows after upgrading to confirm expected behavior in your environment.

  • Monitor high-volume log search scenarios and use focused filters when working with very large execution logs.

  • Test API-triggered Hyper Flows after adding Response Headers to confirm the external system receives the expected headers.

  • Use the rerun mechanism for controlled troubleshooting instead of manually recreating failed executions.

PreviousCanakkale 5.5.1
NextCanakkale 5.7.0

Was this helpful?