> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/release-notes/canakkale-edition/canakkale-5.7.0.md).

# Canakkale 5.7.0

## Release Summary

Autom Mate Canakkale 5.7.0 focuses on user-facing notification experiences, Mate Agent observability, in-product engagement, and stability across scheduling, data handling, and access control.

This release introduces a global notification framework that lets administrators create, update, and schedule notifications from a central admin screen and display them across all Autom Mate interfaces, with per-user read tracking and a listable modal. It also adds a Mate Agent RAM and CPU metrics modal for quick resource monitoring, and a collapsible Community news panel that surfaces Community updates directly inside the product.

Canakkale 5.7.0 also improves the notification panel experience with an unread-first view and paginated “View All” exploration, and refreshes the Dashboard Summary Mail with an updated Automation Impact Report template and expanded field mapping.

Several stability and correctness issues have been resolved, including a backend crash caused by unsupported scheduling timezones, object variable corruption in the Object - Assign action, an unclickable API Key Generate popup after visiting the AI Agent Composer, an unresponsive notifications page under high notification volume, and a License Management role enforcement gap. Trigger Param previews have also been improved with a hierarchical object viewer and Base64 truncation.

Overall, Canakkale 5.7.0 strengthens platform stability, improves resource visibility, and continues to refine the everyday notification and engagement experience across Autom Mate.

***

## **Highlights of this Release**

### 🅱️ **Bug Fixes**

* Fixed backend crash when scheduled automations use an unsupported timezone.
* Fixed Object - Assign action accepting non-object values and corrupting object variable types.
* Fixed API Key Generate popup buttons becoming unclickable after visiting the AI Agent Composer.
* Fixed notifications page becoming unresponsive under high notification volume.
* Fixed License Management update actions being available to users without the update role.
* Improved Trigger Param preview with a hierarchical object viewer and Base64 truncation.

***

### ✨ **New Features**

* Global notification management and display across all Autom Mate interfaces.
* Mate Agent RAM and CPU metrics modal.
* Collapsible Community news panel.

***

### 🛠️ **Enhancements**

* Notification panel unread-first display with paginated “View All” view.
* Dashboard Summary Mail updated with the new Automation Impact Report template.

***

## **Detailed Version**

{% tabs %}
{% tab title="🅱️ Bug Fix" %}

* #### Scheduled Automations Crash Backend on Unsupported Timezone

  Creating or executing a scheduled automation could crash the backend when the selected timezone was not supported by the scheduling package, for example `America/Guayaquil`, causing an uncaught exception during execution.

  Timezone validation is now performed before an automation is saved or scheduled, the selectable timezone list is aligned with the backend-supported list, and unsupported values return a clear validation error instead of reaching runtime and crashing the service.

***

* #### Object - Assign Action Corrupts Object Variable Type

  Entering a non-object value such as a string, number, or boolean into the `item` field of the Object - Assign action completed successfully and wrote the invalid value into the object variable, corrupting its expected type.

  Input validation has been added on both the UI and runtime sides so only valid object data is accepted. Invalid data types no longer update the variable and now return a clear error message indicating that an `object` is expected, while existing valid use cases continue to work.

***

* #### API Key Generate Popup Buttons Unclickable After AI Agent Composer

  After visiting the AI Agent Composer tab and navigating elsewhere, opening the Help > API Key Generate popup left its buttons unclickable due to a leftover overlay, focus trap, or z-index conflict persisting after the page transition.

  The lingering interaction blocker has been resolved so the Generate New Key, Cancel, and OK buttons work reliably in the post–AI Agent Composer navigation scenario across browsers.

***

* #### Notifications Page Unresponsive Under High Volume

  On environments with very large notification counts, opening the notifications pop-up failed to load and eventually made the page unresponsive.

  Notification display is now limited so the pop-up opens reliably regardless of how many notifications exist for the user, preventing the page from freezing.

***

* #### License Management Update Role Not Enforced

  Users without the update role could still see and use License Management actions such as adding a license file and validating it.

  Role enforcement has been corrected so update-only actions are hidden and blocked for users who do not have the required update permission.

***

* #### Trigger Param Preview Object Viewer and Base64 Truncation

  In the Trigger Param detail screen, the Trigger Body and Trigger Header preview areas displayed object data as plain text and fully rendered long Base64 content, reducing readability and risking performance issues with files or images.

  Trigger Body and Trigger Header previews now display object data using the same hierarchical object viewer as the Object Assign action output. Long Base64 values are clearly identified and truncated, file metadata fields are shown as separate object fields, and existing JSON, object, array, and string preview behavior remains backward compatible.
  {% endtab %}

{% tab title="✨ New Features" %}

* #### Global Notification Management

  A global notification structure has been introduced so notifications can be displayed across all Autommate interfaces.

  Administrators can create, update, and delete notifications from a new Notification Admin screen in the global project and optionally define a display date range. Only notifications matching the active date range are shown, users can mark notifications as read with read status stored per user, and all global notifications are listable in a modal. Access to the admin screen is restricted to authorized users.

***

* #### MateAgent RAM and CPU Metrics Modal

  A new modal displays MateAgent resource usage so users can quickly monitor system load.

  For each MateAgent, the modal shows RAM usage, CPU usage, status, and last updated time in a readable and comparable format, with loading and error/empty states, following the existing UI/UX design.

***

* #### Collapsible Community News Panel

  A collapsible panel has been added to surface Community news directly inside the product.

  The panel lists Community news items with a title and short description or date, expands and collapses without interfering with normal screen usage, and redirects users to the related Community page when a news item is clicked.
  {% endtab %}

{% tab title="🛠️ Enhancements" %}

* #### Notification Panel Display and Pagination

  The notification panel now opens with a focused, unread-first view.

  When opened, the panel shows only the latest 10 unread notifications, with an appropriate empty state when there are none. A “View All” button opens a large, fullscreen modal that lists all notifications with pagination, keeping the initial panel load optimized while allowing detailed exploration.

***

* #### Dashboard Summary Mail Template Update

  The Dashboard Summary Mail has been updated with a new Automation Impact Report template based on internal and customer feedback.

  The email now uses the subject `{{report_period}} Automation Impact Report` and an expanded body field mapping, including tasks automated, active automations, time recovered in hours and days, total business impact, and a link to the public dashboard.
  {% endtab %}
  {% endtabs %}

***

## User Notices & Guidance

This section highlights important behavioral changes, usage recommendations, and practical tips introduced in Canakkale 5.7.0. Reviewing these notes will help users adopt the new global notification framework, updated notification panel, Mate Agent monitoring, and the refreshed Dashboard Summary Mail smoothly.

{% hint style="danger" %}

#### Warnings (Critical Behavior Changes)

* **Scheduled Timezone Validation**\
  Scheduled automations now validate timezones before saving or execution. Unsupported timezones are rejected with a clear validation error, and the selectable timezone list is aligned with the backend-supported list.
* **Object - Assign Input Validation**\
  The Object - Assign action now rejects non-object values in the `item` field. Assignments with invalid data types will fail with an error instead of silently corrupting the object variable.
* **License Management Permissions**\
  License Management update actions are now enforced by role. Users without the update role will no longer see or be able to use add and validate license actions.
* **Notification Display Limits**\
  Notification pop-ups now limit how many items are shown to keep the page responsive under high notification volume.
  {% endhint %}

***

{% hint style="info" %}

#### Hints (Productivity Tips)

* Use the **Notification Admin screen** in the global project to broadcast notifications across all Autom Mate interfaces, with an optional display date range.
* Use the **Mate Agent metrics modal** to quickly check RAM, CPU, status, and last updated time for each Mate Agent.
* Use the **Community news panel** to stay up to date with Community announcements without leaving the product.
* Use **“View All”** in the notification panel to open the full, paginated notification history in a large modal.
* Review the updated **Automation Impact Report** email to see period-based tasks automated, active automations, time recovered, and business impact at a glance.
  {% endhint %}

***

{% hint style="success" %}

#### Best Practices (Recommended Usage)

* After upgrading, review scheduled automations that used custom timezones to confirm they remain valid against the supported timezone list.
* Validate existing Object - Assign steps to confirm they pass valid object data now that input validation is enforced.
* Confirm License Management access for each role after upgrading to verify update permissions behave as expected.
* Use the global notification date range to schedule announcements so they appear only during the intended period.
  {% endhint %}