Alumio version 3.1120.0-RC1 brings a mix of platform-level improvements and key fixes. We’ve added direct Azure Blob Storage support in the Filesystem, improved visibility into storage usage, and laid the groundwork for upcoming features with dependency updates. Alongside that, we’ve addressed several edge cases around task execution, routing, and UI consistency to make integrations behave more predictably. We’ve also included connector updates to two popular systems!
What’s new and improved with Alumio version 3.112.0-RC1:
Access Azure Blob Storage directly via the Filesystem
You can now connect to Azure Blob Storage directly through the Filesystem interface, removing the need to configure a separate HTTP Client. This simplifies setup and makes working with Azure storage more straightforward.
Monitor storage size from the overview page
It’s now possible to view the size of storage configurations directly within the Storage overview page, giving better visibility into usage.
Dependency updates to support upcoming platform improvements
We’ve updated several core dependencies to prepare the platform for upcoming improvements, including AI-related capabilities. This update has no impact on existing functionality.
Unique identifiers assigned to existing configurations
Existing configurations are now automatically assigned unique identifiers, enabling platform-wide linking without requiring users to resave records manually.
More robust handling of SOAP responses
Fixed a bug where SOAP publishers and transformers could fail when receiving non-iterable responses. The process now continues as long as the response can be parsed.
Prevent duplicate task execution in real-time routes
Resolved an issue where tasks in real-time routes could be executed twice due to a timing gap between task creation and the “Processing” status update.
“Run route” action now executes reliably
Fixed a bug on the Route detail page where the Run route action would fail with a log error instead of triggering execution.
Correct message placement for Waiting task updates
Solved an issue where messages updating Waiting tasks were incorrectly shown in the Import tab instead of the Export messages tab.
Restored icons in the Code transformer editor
Fixed an issue where icons were missing in the Code transformer editor, restoring proper UI visibility.
Connector updates
The following connectors have been updated with the new version:
- Sendcloud connector, v3.
- Channable connector, v2.
Release dates
- Release candidate 3.112.0-RC1 will be installed in week 18 (sandbox environments)
- Stable release 3.112.0 will be installed in week 20 (production environments)
- Important: these dates apply only to environments configured with the ‘Latest’ update cycle.
Update cycles
Alumio offers two update cycles to choose from. By default, your environment is set to the “Latest” update cycle.
Latest
With the “Latest” update cycle, your environment will always receive the most recent version of Alumio. Updates are first deployed to sandbox environments. Two weeks later, the same version is released to production environments. Every 2 weeks a new version of Alumio is released.
Long-Term Support (LTS)
The LTS version is released quarterly and is based on a thoroughly tested Alumio release that is a few versions behind the latest version, providing extra stability and security. However, selecting this option also means you won’t have access to any newly released Alumio features for a period of three months.
Sandbox environments (such as UAT) receive the LTS version one month before the start of the new quarter (i.e. June), specifically on the first Monday of that month.
The LTS version is deployed to production environments on the first Monday of each new quarter (i.e. July). This provides a full month for testing prior to deploying the new LTS version to production.
You can switch your update cycle through the Alumio interface
- Log in to your Alumio environment.
- Navigate to System > Settings.
- Modify the Update Cycle setting and click Apply to save your changes.