Welcome back to the Maia New Features Blog! This week, we're excited to introduce the Upgrade Assistant, a powerful new tool designed to streamline your migration experience and make transitioning to Maia smoother than ever.

✨ Migrate to Maia with our new Upgrade Assistant

We're excited to announce the Upgrade Assistant, a powerful new tool within Maia that simplifies and streamlines the migration of Matillion ETL workloads.

This new feature lets you connect Maia directly to your existing Matillion ETL instances, which makes it easier and quicker to migrate your workloads to Maia. With the Upgrade Assistant, you can:

• Migrate schedules, jobs, secret references, shared jobs, API Extract profiles and API Query profiles
• Configure advanced import options, including migrating Python workloads to Script Pushdown components
• Create custom connectors automatically from API Extract profiles
• Migrate shared jobs without needing to create custom mapping documents

Ready to get started? Check out the Upgrade Assistant documentation!

💬 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.

Welcome back to the Maia New Features Blog! This week, we're excited to introduce Impact Stream, a game-changing feature that transforms how you handle pipeline failures by automatically surfacing downstream dependencies right when you need them most.

🔍 Trace dependencies in seconds with Impact Stream

When a pipeline fails, there’s always one question that your engineers need to answer: What else is affected? Until now, answering that required previous tribal knowledge or manual review—locating the failed dataset and tracing dependencies by hand.

Impact Stream solves this problem. It surfaces downstream dependency information automatically at the moment of a pipeline failure, with no manual lineage navigation required. It’s made up of two parts:

• Pipeline tree: The pipeline tree on the left shows the hierarchy of pipelines involved in the run, starting from the root pipeline. Each node displays the orchestration or transformation pipeline’s name, its environment, and a colored dot indicating its status.
• Impact Stream canvas: When lineage is available, the Impact Stream canvas shows how datasets and pipelines connect to one another, with arrows showing the direction of data flow. Each node is outlined in a color indicating its status:
  • 🔴 Failed:The pipeline or dataset encountered an error
  • 🟡 Potentially affected: The pipeline or dataset is downstream of the failure and may be affected, but wasn't directly executed
  • ⚪ Unaffected: The pipeline or dataset has no dependency relationship with the failure
  • 🟢 Success: The pipeline or dataset was processed without error
  • Not executed: The pipeline or dataset didn't run as part of this execution

To access a failed pipeline’s impact stream, in the left navigation, click Activity, then Pipeline runs. Click the target icon next to any failed run to view its impact stream.

It’s important to note that Impact Stream isn't a replacement for Lineage. Lineage is your always-on, comprehensive dependency map. Impact Stream is a run-specific, on-demand triage view, scoped to a single failure, generated instantly.

For more information, read our Impact Stream guide.

💬 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.

‍

This week, we're focusing on making your Maia experience smoother and more efficient. We've introduced a major performance upgrade for Designer, streamlined selecting items when configuring components, and added new connectors to expand your data loading capabilities. Check out the changelog updates for all the details.

🎨 Mission Control gets a new look

You can now switch between two views in Mission Control: the classic Kanban view and our new List view.

List view is designed to help you keep track of your work when you’re juggling a lot of Mission Control tasks, by highlighting tasks that need your attention. Whenever Maia Team needs your help or asks you to review a completed task, these tasks are stacked at the top of the new view by default.

Use the view toggle in the top right of your Mission Control board to switch between List view and Kanban view. Maia remembers your choice, so your Mission Control board will always open to your most recently selected view.

One more update—it’s now super easy to rename Mission Control tasks to help you keep track of the work being done in each task.

Keen to get started? Check out the Mission Control documentation.

⏩ Designer performance improvements

The pipeline canvas now runs up to 14× faster, with a particular impact on Windows enterprise hardware, giving you a noticeably smoother experience when you're moving items around the canvas, updating pipelines, and browsing files in large projects.

🎯 Configure components without losing sight of your work

Every dual listbox style component property has been upgraded. The new design of these properties lets you select one or more items from a list in the component properties panel, without a dialog blocking your view of the canvas.

As a result, you never lose sight of your pipeline and other Designer elements, such as the Maia Team chat panel and Variables tab, when configuring components. This gives you a fully in-context, uninterrupted configuration experience.

🔌 New connectors

We’ve released the following new connectors this week, making it easier than ever to bring data from these sources into your Maia projects.

For all projects:

• Google Analytics

For Snowflake and Google BigQuery projects:

• Amazon DynamoDB Load
• Bing Ads Load
• ElasticSearch Load
• Excel Load
• Facebook Ads
• SharePoint Load
• Stripe Load
• Zoho CRM Load

Click the name of a connector in the list above to learn more about each one!

💬 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.

This week, we're bringing you powerful new capabilities that enhance flexibility and streamline your workflows in Maia. From dedicated script runners to seamless repository migrations and improved pipeline management, these updates are designed to make your data operations more efficient and adaptable. For a full list of recent changes, check our changelog updates.

💻 Script Pushdown component and runner

We're excited to announce an upgrade that allows you to run Python and Bash scripts in a dedicated runner when using a Hybrid SaaS deployment.

This new feature provides allows you to:

• Have a dedicated script runner that is scaled appropriately for these workloads, keeping your Maia runner scaled for average task loads.
• Deploy this script runner as part of your Maia runner deployment.
• Use your existing process to load libraries.
• Migrate large script workloads from Matillion ETL when upgrading to Maia without adjusting for runner architecture.

As part of this change, we've also introduced sizing options for both script runners and Maia runners.

The Script Pushdown component supersedes the Bash Pushdown component. The Python Script and Python Pushdown components are not affected. Python Script can still be used for smaller workloads that do not impact your Maia runner, and Python Pushdown is still used for Full SaaS deployments.

Read the Script Pushdown component guide to learn more.

🔄 Migrate your project’s repository using our API

The new Migrate Repository API endpoints gives you more flexibility than ever. You can now change the repository that your Maia project is based on.

Whether you’ve department switched Git providers or you need to move away from a hosted repository, the Maia API supports migrations from hosted Git to GitHub, GitLab, and Azure, as well as between GitHub, GitLab, and Azure providers. This means you can adapt to organizational changes without losing your project progress or having to start from scratch.

Read our Repository Migration API guide to get started.

✍️ Automatically update pipeline references

When renaming a pipeline in Designer, you can now ask Maia to update all references to the renamed pipeline in other pipelines in your project—for example, if you rename an orchestration pipeline that’s referred to in a Run Orchestration component in another pipeline.

This update streamlines project management by automatically updating all pipeline references, eliminating the need to manually track down and update these references, saving time, and reducing the risk of broken links when reorganizing your pipelines.

💬 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.

‍

Welcome back to the Maia New Features Blog! This week's changelog updates bring several major updates designed to enhance pipeline flexibility, improve collaboration, and make your experience with Maia AI Agents smoother than ever. Let’s dive into the details.

🤖 New Mission Control features

Mission Control just got even more efficient! This week’s updates help you to keep your work moving at pace, while ensuring you stay informed about all the tasks Maia AI Agents are working on.

🔔 Slack notifications

You can now get a Slack alert as soon as Maia AI Agents need your help–no need to keep Mission Control open to monitor their progress.

A task moves to the Needs Attention column of your Mission Control board when Maia AI Agents stop–because they’ve finished their task, they need you to approve a tool action, or they’re waiting on input from you. With Slack notifications, you’re in the loop as soon as they need your attention, enabling you to respond quickly and keep things moving.

To set up alerts, click Slack notifications in Mission Control, toggle notifications on, and enter a Slack incoming webhook URL. You’ll see a checkmark next to the notifications icon when they’re active. Pause and resume notifications at any time using the toggle.

Ready to get started? Read our guide to Slack notifications for Mission Control.

🎯 New Balanced permission level

We've introduced a new Balanced permission level for Mission Control that lets Maia AI Agents move faster on the safe stuff while still checking in before making any big decisions

You can now choose between three preset permission levels when giving Maia AI Agents a task:

• Go with Ask permission if you want full control over Maia AI Agents’ work–they’ll ask for permission to do anything beyond reading and editing files.
• Choose Balanced to let Maia AI Agents get on with recoverable work on their own, while still stopping to ask when it really matters.
• Pick Full access when you’re giving Maia AI Agents trusted, hands-off tasks, such as prototyping or work in a sandbox environment.

For more details about all the permission levels in Mission Control, read Permission levels.

🔄 Maia AI Agents support shared pipelines

When you ask Maia AI Agents to build a new orchestration pipeline, whether in Designer or Mission Control, they now find and use suitable shared pipelines, instead of rebuilding the same thing from scratch.

If there's a clear match, Maia AI Agents will simply use a Run Shared Pipeline component to use the available pipeline. If there are multiple candidates, they’ll ask you to choose which one to use. And of course, if Maia AI Agents can’t find a matching shared pipeline, they’ll get started building your new pipeline as usual!

For more information, read the Orchestration pipelines section of our guide to building pipelines with Maia AI Agents.

🔎 Enhanced usage and billing insights

We’ve updated the usage dashboard and released credit budgets to give your teams more detailed information than ever before about your credit consumption and usage. These features are available for users with the Manage Billing permission.

📊 Dive into your usage dashboard

We've made significant upgrades to your usage dashboard to provide deeper visibility into where your credits are being spent. The usage dashboard now features:

• Flexible date ranges: View consumption over preset ranges (last 7 days, last 30 days, monthly, quarterly), or select a custom range.
• Consumption overview graph: See your remaining credits and the credits you’ve used this billing period at a glance.
• Feature-level breakdown: Toggle between credit breakdowns by orchestration, transformation, and additional users, each showing the total credits used and their percentage of your total consumption.
• Project and pipeline breakdown: Filter by project, environment, and feature, then use the sort and search options, to see credit usage at the individual pipeline level.
• Daily breakdown: Drill down into any pipeline or user's consumption on a day-by-day basis.

Check out the Usage dashboard documentation to learn more.

💰 Budgets and alerts

You can now create budgets and set credit usage thresholds to monitor your credit consumption and receive an alert when you approach or exceed your allowance.

You can set two types of budget:

• Global budget: Track your total credit consumption across every project in your account, scoped to your current contract period.
• Project-level budgets: Set a credit consumption limit for one or more individual projects and track their consumption.

For each of your budgets, you can set one or two usage thresholds as percentages of the corresponding credit consumption limit. Then, set up billing notifications to receive an alert by Email, Slack, or Webhook when your usage exceeds any of these thresholds.

Budgets and thresholds are informational only–they don't restrict usage. For more information, read Budgets and alerts and Billing notifications.

💬 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.

Welcome back to the Maia New Features Blog! This week, we're excited to bring you updates that give you greater control and visibility over your pipeline operations. We've introduced enhanced status tracking so you can see exactly what's happening with your pipeline steps, plus new concurrency controls for iterators to help you optimize performance. For a full list of recent changes, be sure to check our changelog updates.

🚦 New “Pending” status for pipelines

When checking a pipeline’s status using your pipeline run history, task history, or the Maia API, you can now see the difference between a pipeline step that's actively executing and one that's waiting for a runner slot.

Steps will only show as Running when they're actively executing. Before that point, they'll show as Pending, so you'll always know whether something is genuinely in flight or just waiting. As tasks are picked up, pending tasks move to running in real time. This makes it easier to diagnose whether a slowdown was a real execution issue or just queue pressure.

Read the documentation to learn more about viewing step execution status.

🔁 Maximum concurrency limits for iterators

You can now set a maximum number of concurrent iterations on any iterator in Maia, giving you more flexible control over how pipelines are executed. This allows you to:

• Control concurrency: Previously, you had to choose between full concurrency of the available runner capacity or fully sequential runs. Now you can set a sensible concurrency level that gives you optimal performance without overwhelming your downstream systems or data warehouse.
• Import Matillion ETL pipelines with sensible defaults: Apply a sensible max concurrent iterations when importing pipelines, ensuring there are no unintended consequences of Maia’s greater scalability.

For customers upgrading from Matillion TL to Maia specifically, we are introducing a default of 16 when importing a pipeline into Maia. You can be change this setting or completely turn off the limit when setting your import preferences.

⚠️ Watch out for iterator stacking—limits are multiplicative, not additive. Stacked iterators can hit full runner capacity quickly if not configured carefully.

💬 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.

‍