With the release of Alumio version 3.107.0-RC1, we’ve focused on stronger control over API usage, clearer system feedback, and more predictable runtime behavior. Several improvements reduce ambiguity in monitoring and logging, while others strengthen integration security and file handling. The result is better governance, improved reliability, and fewer edge-case surprises in production environments.
Here’s what’s new and improved with Alumio version 3.107.0-RC1:
Improved API token management and visibility
Our API token management now includes creator tracking, usage insights, direct delete actions, consistent row actions, and clearer copy confirmations. In other words, teams can see who created a token, understand how it is used, and remove unused credentials without friction. This improves governance and traceability.
Clear indicator for unlimited tasks and improved email date formatting
The Statistics tab now shows a visual indicator when tasks are unlimited. Additionally, we’ve improved date formatting in email alerts to avoid ambiguity. This reduces misinterpretation of capacity limits and avoids confusion in time-sensitive alerts, particularly across regions using different date formats.
HTTP Proxy support for request signature validation
Request signature validation is now available for the HTTP Proxy through a new request processor. It supports the same validators used for Webhook validation, enabling secure and reliable integrations.
New scheduler log status for skipped or overlapping jobs
We’ve added a new scheduler log status to indicate when a scheduled job is skipped or failed while a similar job is already running. This makes concurrency safeguards visible, improving troubleshooting and operational clarity during parallel executions.
More flexible HTTP logging controls
HTTP logging can now be enabled or disabled more granularly. A new “Enabled logging” dropdown is available in the HTTP transformer, subscriber, and publisher, in addition to existing plugin and checkbox options in HTTP clients and requests.
Filename sanitization for FTP via HTTP Filesystem
When writing files to FTP via the HTTP Filesystem, it’s now possible to sanitize filenames. This includes a configurable destination filename field with placeholder support.
Transformer tester UI redesign
We’ve implemented the new design for the Transformer tester, ensuring it works smoothly across different screen sizes. This improves usability during development and testing, especially for teams working on smaller screens or in split-view environments.
Release dates
- Release candidate 3.107.0-RC1: will be installed in week 08 (sandbox environments)
- Stable release 3.107.0: will be installed in week 10 (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.