Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.alumio.com/llms.txt

Use this file to discover all available pages before exploring further.

Bc5a40d5e68e6f530ac2a0b66a672cfdd0aa6536 2 1380x308
As 2025 comes to a close, Alumio version 3.103.0-RC1 delivers a useful new tool that allows you to send emails directly from integration flows. We’re also including a set of practical improvements and fixes for several issues that would otherwise mislead monitoring, waste time during cleanup, or break integrations unexpectedly. Stay tuned for some of the bigger features we’re working on for upcoming releases and the new year ahead—in our quest to make integrations simple.

​
Here’s what’s new and improved with Alumio version 3.103.0-RC1:

​
Send emails directly from your integration flows

We’re happy to introduce our new Email Transformer that allows users to send fully configurable emails directly from integration flows. This makes it easier to trigger automated notifications and reports without relying on external systems.
Image

​
Delete large configurations without running out of memory

We’ve improved the configuration usage check to handle large configurations efficiently. This prevents out-of-memory errors when deleting configurations with extensive data (such as Transformer tests).

​
Dashboard error counts now match reality

We resolved an issue where parsing warnings were incorrectly counted as errors. This caused the dashboard error graph to show inflated numbers that didn’t align with the actual error list.

​
Deleting users no longer breaks live API integrations

We fixed an issue where deleting a user would immediately revoke their API keys. This could potentially break active integrations without warning. Now API keys are no longer invalidated when the user is removed.
Fixed a Google Cloud Storage Incoming edge case Another issue we resolved involved the Incoming Configuration throwing an exception after successfully using “Write all items to a storage” for Google Cloud Storage. This caused the run to fail even though the write had completed. Release dates
  • Release candidate 3.103.0-RC1: will be installed in week 52 (sandbox environments)
  • Stable release 3.103.0: will be installed in week 54 (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
  1. Log in to your Alumio environment.
  2. Navigate to System > Settings.
  3. Modify the Update Cycle setting and click Apply to save your changes.