🚀 Enhanced Maia Agents, Expanded Workload Conversion, and Pipeline Visibility

This week, we're excited to share several powerful updates that will enhance your experience with Maia, expand your migration options, and provide better visibility into your pipeline operations.

🤖 Maia agents update: Automatic plan mode and dedicated pipeline validation

We're happy to introduce two improvements to how Maia works.

What's new?

• Automatic plan mode: Maia can now enter plan mode on its own when it determines a task is complex enough to warrant planning. It will explore your project, create a detailed plan, and present it for your review—approve it to proceed, or request changes.
• Dedicated pipeline validation: Pipeline validation is now a standalone action rather than just a side effect of editing. Maia can check your pipeline components against the warehouse at any time, making it better at understanding and diagnosing configuration errors, invalid options, and missing references—even when it isn't actively editing.

How do you use it? Both improvements activate automatically. Maia will ask your permission before entering plan mode, and can validate pipelines independently whenever it needs to investigate issues.

🔄 Expanded competitor support for Convert Workloads tool

The Convert Workloads tool now supports four additional competitor platforms: IBM DataStage, Oracle ODI, Wherescape, and Apache NiFi, all available in Public Preview. This expansion brings the total number of supported competitor products to 15, making it easier than ever to migrate your existing data workflows to Maia.

With this enhanced compatibility, you can seamlessly transition from a wider range of platforms while reducing manual work in the conversion process. The tool automatically translates your existing workloads, helping you speed up your migration and reduce implementation complexity.

Documentation on the conversion process can be found here.

🚀 Better visibility for pipeline runs

We know that searching for a specific failure in a sea of "Red" can feel like finding a needle in a haystack, especially when a single pipeline is failing multiple times a day.

To save you from the manual scroll and give you better insight into your schedules, we've shipped two updates to Pipeline Run History:

Search by execution ID: Stop "trawling" and start finding. If you already have the specific execution ID from a log or an alert, you no longer need to filter by pipeline name and guess the timestamp.

• The change: The search bar now accepts full pipeline execution IDs.
• The benefit: Instant access to the exact run you're investigating. No more manual sorting through dozens of identical-looking runs.

Visibility into skipped pipelines: Previously, if a schedule tried to trigger but was blocked by concurrency config, it vanished. Now, you have the paper trail.

When a schedule has Allow concurrent executions set to False, and a new run is requested while the previous one is still active, we now log and display that attempt as Skipped.

• The indicator: Look for the amber status tag in the Pipeline Runs screen.
• The why: We've added specific execution messages to pinpoint the blocker: "Skipped because allow concurrent execution is false and execution [ID] is still in progress."

🤖 Maia update: Smarter conversation titles

A small quality-of-life improvement—conversation titles now update as you chat, so they always reflect what you're actually discussing, not just your first message.

What's new?

• Dynamic titles: Titles regenerate using your recent message history, staying relevant as conversations evolve.

How do I use it? No action needed—this works automatically for all conversations.

💬 We'd love to hear from you!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

Want to get involved? Join the Matillion Community to stay up to date, share feedback, and help shape our product roadmap for future innovations.

‍