Page cover image

Boston 4.3.2

📅 Release Date: December 6, 2024 - 📅 Next Release Date: December 13, 2024

🚀 Highlights of this Release

This release introduces a self-healing mechanism for failed or stuck operations in the Autom list view, implements a global enhancement by renaming "4me" to "Xurrent," and resolves a bug related to the ordering of data in the pending section on the monitoring page.

🅱️ Bug Fixes

📌 Correct Order for Pending Change Orders

Fixed an issue where the data in the Pending section on the monitoring page was listed in descending order (DESC) by created_at. It is now displayed in ascending order (ASC) as expected.


🛠️ Enhancement

📌 Global Renaming

Updated the global instance to replace all references of "4me" with "Xurrent."


✨ New Features

📌 Self-Healing for Failed and In-Progress Operations

  • A new feature designed to handle operations that fail or remain stuck in the "In Progress" phase.

  • Users can retry the operation using a new Retry Icon that appears in the corresponding row in the Autom list view.

Hint

  • The self-healing feature applies only to webhook-triggered Autom operations in the Autom list view.

  • Ensure your operations are triggered via webhook to utilize this feature effectively.

  • For recurring failures, review your Autom configuration or webhook setup.

  • This feature is exclusive to the Autom list view and works only for webhook-triggered operations.


Detailed Version

Correct Order for Pending Change Orders

  • Issue: Data in the Pending section on the monitoring page was being listed in descending order (created_at DESC) instead of ascending order (created_at ASC).

  • Solution: The default sorting behavior has been corrected to display the oldest entries first (ascending order).

  • Impact: This fix improves the usability of the pending section by ensuring logical data presentation and easier tracking of the oldest pending change orders.

Last updated

Was this helpful?