We are conducting critical research to understand how your team actually decides where new data work goes, and what it takes to get that work delivered.

This isn't a pitch or a product feedback session; it's a deep dive into your day-to-day decisions, workflows, and priorities, focusing purely on how data requests move from "someone asked for this" to "it's running in production." We want to understand how you work, not just which tools you use.

🎯 The core job

The goal of this discussion is to understand the complete process behind: "Deciding where a new piece of data work should go, and getting it delivered fast enough to actually matter, whichever tool ends up doing the work."

💬 What we will discuss

This 30 minute session will be confidential and conversational, covering your process from start to finish, regardless of which tools you currently use:

1. The day job: What's your role's responsibility when a new data request comes in? Who decides where it gets built?
2. The workflow: Walk us through the last new data request your team received, start to finish. Which tools ended up touching it, and why those ones specifically?
3. The struggles: What's actually stopping more of your team's work from running through a single platform today? What are you running alongside it, and what keeps that arrangement in place?
4. Desired outcomes: If your team never had to think twice about where a new piece of data work should go, what would that look like?

Your insights will directly influence how we invest in Maia, ensuring we build towards how your team actually decides and delivers, not how we assume you do.

📅 Book a call

Book Call with the Matillion Product Team.

Welcome back to the Maia New Features Blog! This week, we're focusing on making your Maia experience smoother and more efficient. We've introduced quality of life improvements for branch management and enhanced our failure notifications to help you respond faster to issues. For a full list of recent changes, be sure to check our changelog updates.

🌿 Quality of life improvements to branches

We've released three quality of life improvements to the Branches page that will streamline your workflow and reduce friction when managing branches:

• Push a branch when you create it: Fewer steps to create and share a branch with your team.
• Delete a branch from local, remote, or both: Keep your workspace clean by removing old branches with more control.
• Branch location indicator: Clear branch status visibility to help you avoid mistakes.

These improvements mean fewer steps in your daily workflow, less clutter from outdated branches, and better visibility into your branch status to help you prevent common errors. For more information, read our Branches guide.

🚨 View Impact Stream directly from failure notifications

A small but valuable improvement to notifications has arrived! Pipeline failure notifications now include a View Impact Stream link that takes you directly to the Impact Stream for that failure, so you don't need to navigate to find it yourself.

This creates a genuinely different kind of alert: not just "something's wrong", but "here's what's at risk." Instead of simply telling you that something’s gone wrong, you can now see what it impacts downstream with one click from the alert straight into the pipeline tree and lineage flow, with downstream datasets already flagged as potentially affected. This makes a real difference to how fast you can triage a failure, especially during critical incidents.

Want to know more? Check out our Impact Stream 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! Check out the changelog for the latest Maia improvements, then read on for a closer look at this week's biggest update.

🔄 Background sampling with persistent results

Sampling no longer blocks you or forgets what you were doing.

Sampling now runs in the background instead of holding up the panel. Leave, and a toast brings you back when it's ready, with a spinning border marking components still sampling. Samples persist when you navigate away, and across components as you sample in a session. Both changes save you time and reduce repetitive actions as you build your pipeline. The panel itself has also been reworked: actions have moved, the Data Cleanse action has moved, and you can add and manage multiple filters on a sample independently.

You can sample several components, step away from the panel, and come back to find every sample exactly as you left it—no need to re-run the same sample for the same component unnecessarily. Running sampling in the background, with clear in-progress and completion signals, means you're never stuck waiting on a response, and multi-filter support lets you narrow a sample from more than one angle at once.

Read Sampling Output to learn more

💬 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, or head over to the Matillion Community to join the conversation.

Great news! Our validation UX improvements are now generally available. These enhancements make pipeline development faster and more efficient by removing previous limitations.

✅ What's new

• Keep building while validation runs: Move on to the next component as soon as it's validated, rather than waiting for the whole pipeline.
• No more validation timeouts: Validations that used to hit the 2-minute cap now run through to completion, however long they take.
• Cancel long-running validations: Cancel directly from Designer whenever you need to.

These improvements mean you can work more efficiently without being blocked by lengthy validation processes, giving you better control over your development workflow.

For a full list of recent changes, be sure to check our changelog updates.

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

This week, we're focusing on making your Maia experience smoother and more efficient. We've made major upgrades to Convert Workloads that prioritize accuracy and transparency.

🔄 Convert Workloads improvements

We've enhanced how Convert Workloads runs so that it prioritizes correctness and delivers more accurate results. Here's what's new:

• Workloads are now preprocessed to remove noise, with the cleaned version written to your branch so Maia Team can review the source workload for debugging if needed.
• A new self-review step double-checks all analysis after processing is complete.
• Detailed progress reporting keeps you updated in real time as Convert Workloads progresses through each analysis stage.

To get started, read Convert workloads from other platforms.

💬 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 excited to bring you powerful updates that enhance collaboration and give you greater control over your development workflow. From redesigned branch management to granular permissions and expanded API capabilities, these features are designed to make your Maia experience more flexible and efficient. Check out the full changelog updates for more details.

🌿 Redesigned branch management

The branches experience has been overhauled to give you more control and visibility over your work.

• The branches page now features new columns giving you more information at a glance, with your default branch pinned to the top of the list for quick access
• Remote branches created directly in your Git repo are now automatically visible in your branch list, so your view is always in sync
• A new merge modal lets you merge from either remote or local branches
• You can create and delete your own branches independently—without sharing them with the whole team or affecting your teammates' work—and clear warnings now surface before any destructive action that could result in lost work
• Environment choice is optional while creating branches. You can now select the environment you want to work on within Designer

Note: delete is an action that cannot be undone

Read the documentation to learn more about the enhanced branch management capabilities.

🏃 Runner management granular permissions

In anticipation of customer roles, granular permissions for runner management are now live.

What's new?

Before, runner management was behind a global manage runners permission. Now, aspects of runner management are governed by specific permissions. Want to give someone permission to edit an allow list without letting them change anything else? Now you can.

How do I use it?

At the moment, these permissions apply to the pre-provisioned roles. Once custom roles are released, you'll be able to create your own roles with the runner permissions you select. This also applies to any public API credentials.

Learn more about account roles in the documentation

💻 Additional connections API endpoints now available

We're also introducing two new API endpoints:

• GET SCHEMA: Retrieve the relevant format for each connection provider, so you can programmatically and dynamically structure your connection requests. For more information, read Get Connection Schema.
• TEST CONNECTIONS: Test a given connection on a specified environment, so you can create and test new environments or test connections as part of your CI/CD pipelines. For more information, read Test a Connection.

💬 We'd love to hear from you!

Let us know how these new features are improving your workflows—we're all ears! Head over to the Matillion Community to share your comments and questions.