Update this pipeline to take into account slowly changing dimensions (type 2 and 3) on core customer attributes
› Thought
Switch to plan mode
✓Maia wants to switch to plan mode
Implementing SCD Type 2 and 3 on customer dimensions requires understanding the current pipeline structure, identifying customer-related components, and determining the best approach for slowly changing dimensions.
› Performed 3 actions
Now I have a clear picture. The pipeline creates a star schema with SQL executors, and DIM_CST_PROF (the customer dimension) needs SCD Type 2 and Type 3 support on core attributes. Let me propose a plan:
✓Maia has a plan for your review
Add SCD Type 2 & 3 to the customer dimension
1Add 5 SCD columns to DIM_CST_PROF
2Type 2 (full history): seg_cd, ltv_idx, sts_flg
3Type 3 (keep previous): eml_ref, ph_hsh
4Seed one historical row (segment change)
5No change to FCT_TXN_LGR
Applying changes to DIM_CST_PROF…
✓Done — DIM_CST_PROF restructured for SCD Type 2 & 3. Review the diff before you commit.
▦ Skills (1) ▾
Ask Maia, use / for commands, or @ to explore more
SELECT TABLE_NAME FROM "JOHN_SMITH"."INFORMATION_SCHEMA".TABLES
› Performed 4 actions
I queried your warehouse and found ACCOUNT, OPPORTUNITY and CONTACT in Snowflake, alongside your Salesforce and Customer 360 data. No existing pipeline matches — I'll build the transformations from scratch.
Building from your context, not a blank slate. I'm applying your GWF standards — the CRM_ table prefix, medallion layer suffixes, and .tran.yaml naming.
Building Sales Performance Metrics.tran — placing components…
✓Built Sales Performance Metrics.tran — 7 components, writing to CRM_SALES_METRICS. Review before you run.
▦ Skills (0) ▾
Ask Maia, use / for commands, or @ to explore more
@ Plan Mode
(x)
⊕
Review ▾ Validate ScheduleRun
Load Opportunities
Load Accounts
Join Opps to Accounts
Calculate Deal Velocity
Sales Metrics by Owner
Calculate Win Rate
Write Sales Metrics
→ CRM_SALES_METRICS
JB
Spring Launch Demo 2026 / dev⑃ dev ▾⌗ Schemas⌕ Search files & quick actions
▤ Files ▾T failed_payment_rate failed_payment_rate.test N
MaiaSelect Knowledge Layer ▾⊕ Add context
Maia
Your team of expert AI agents
◍
Help me build a pipeline
Create a new data pipeline from scratch
◍
Summarize my pipeline
Understand your existing pipeline
▦
Set up a skill for me
Adapt Maia's responses to your workflow
Please create tests for this pipeline
Performed 5 actions
No tests exist yet for this pipeline. I'd like to clarify a few things before creating one:
Maia needs your input1/2
How would you like to set up test data for the PAYMENTS table?
Mock data (Recommended)— create a small set of test rows with known values
Clone existing data— zero-copy clone PAYMENTS into the test schema
Other
Maia needs your input2/2
What should the test verify about the output?
Row count— assert expected number of rows
Column names and types— assert the output schema
Data values— assert specific output values
Performed 6 actions
I've created a separate test pipeline — failed_payment_rate.test — so your original pipeline stays untouched. It spins up an isolated schema, generates mock payments, runs the pipeline, asserts the results, then tears the schema down.
Ask Maia, use / for commands, or @ to explore more
@ Plan Mode
Review ▾Validate ⊘Schedule ◷Run ▶
Failed Payment Rate
Calculates the daily failure rate per payment processor. Groups payments by date and processor, counts total vs failed, then writes results to payment_failure_summary.
Failed Payment Rate Test
Creates mock PAYMENTS data with known failure rates, runs the pipeline in a temporary schema, then asserts: 3 output rows, correct failure rates, expected column schema.
Troubleshoot with Maia. Review root causes and see recommended fixes.
Summary of issue(s)
The pipeline is failing because a target column SEGMENT_CD is expected but not present in the data being processed. This error occurs during query execution with variables in Snowflake. [MLUserError] Target column SEGMENT_CD is not present in the data. Issues in detail — Issue 1: Missing target column SEGMENT_CD …
The pipeline is failing because a target column SEGMENT_CD is expected but not present in the data being processed. This error occurs during query execution with variables in Snowflake.
[MLUserError] Target column `SEGMENT_CD` is not present in the data.
Issues in detail
Issue 1: Missing target column SEGMENT_CD in data
Category: Data Fixable in pipeline:Yes — update the pipeline to either provide the missing column or adjust the query/transformation logic.
MMatillion
Threads
Direct messages
Channels
# general
# engineering
# data-eng-alerts 1
# data-platform
# product
# releases
# data-eng-alertsMaia pipeline health · production · automated alerts only
Wednesday, 7 May
Maia APP7:22 AM
🔴 Schema drift — campaign_lead_enrichment
Column renamed in the Salesforce source broke the pipeline reference — run failed. Downstream pipelines on hold. Fix task created in Mission Control.
Maia Team is a set of expert AI agents that work continuously across the data lifecycle, mapped to real data team roles.
Data Quality
Shift-left data quality that validates and cleanses to keep integrations trusted and resilient
Data Engineering
Design, build and maintain data pipelines, end-to-end within a secure, governed architecture
Connectivity
Connect, extract and sync from anywhere, integrate everywhere - with APIs, secure authentication and reverse ETL
DataOps
Keep data flowing: pinpoint failures, automate debugging, RCA and remediation to own your SLAs
FinOps
Cut costs, spot bottlenecks: performance tuning and optimization to keep data pipelines under budget
Migration
Quick, automated migration from legacy ETL/ELT to transparent, testable, cloud-ready data pipelines
Automate manual data work
AI demand is rising fast, but manual data work slows teams down-Maia automates the work so teams can shift from maintenance to building what matters and turning more ideas into business impact.
Without Maia
Hard-coded pipelines and brittle models
Manual backfills, fixes, and documentation
Weeks to deliver new datasets
Drowning in ad-hoc requests
No time for strategic work
Fragmented tech stack
With
Delegate pipeline creation and changes via prompt
Maintain documentation automatically
Embed agentic data engineers directly with analytics teams
Scale pipelines and teams without adding headcount
Fulfill data requests in hours, not weeks
Migrate and modernize legacy systems with AI
“Maia offers a glimpse into the future of data engineering. It’s intuitive, powerful, and feels like a real accelerant for how teams build with data.”
Sridhar Ramaswamy
CEO at Snowflake
Enable every data use case
Code conversion
Migrate and optimize legacy code
SQL, SparkSQL, dbt and Python optimization and conversion
Data quality and data ops
Data cleaning and preparation
Git based data ops
CICD pipeline that includes auditability, auto-documentation and lineage
Legacy ETL migration
Convert from Alteryx, Informatica, Talend and Qlik to the cloud
Reduce costs and modernize for AI
Data engineering and analysis
ETL/ELT development
Citizen data engineering for data analysts
Pipeline optimization for existing processes
AI-native foundation powering Maia
Maia Foundation provides enterprise data tools for any workload with built-in security, elastic scale, and centralized control.
Maia automates manual data work for teams at global enterprises and fast-growing startups alike.
“Maia is helping us become an AI-ready organization by transforming how we build pipelines. In some cases we’ve seen pipeline build time go from 2 days to 10 minutes.”
John Tentomas
CEO Nature’s Touch
Roberto Lara
VP of Digital Transformation & Analytics
Precision Medicine Group
“The biggest impact of Maia is our data engineers embracing it and helping us work smarter, not harder.”
Ammad Baig
Director of Enterprise Data & AI Services
Precision Medicine Group
"Maia is like having an autonomous data engineering team in digital form. It handles everything from legacy ETL migrations to building complex, production-ready pipelines at machine speed, and the quality of the logic is something we can trust. It’s dramatically accelerating our workflow while reducing the manual overhead."
Global Head of Data Transformation
"With Maia, our teams no longer wait in queues for data. Business users are self-serving insights securely, and our engineering team is now focused on strategy, not support. It’s the first real GenAI platform that understands our data reality."
Chief Data Officer
Insurance Company
This is a reimagining of data engineering and ETL - we’re rethinking what’s possible. With Maia, our analysts can build and debug complex pipelines using natural language, whether in the UI or directly in SQL and Python. It’s incredible to see non-engineers creating production-ready workflows without relying on our dev team.
“Maia replaced thousands of hours of manual work, helped us de-risk audits, and let business teams generate insights in days instead of months. It’s the first AI investment that delivered value fast.”
Group CFO
Global Financial Services Firm
"Maia feels like having a team of junior data engineers who never sleep. We’re a small team, but with Maia we’re punching well above our weight."