. The previous limitation was just 1 field.

2\. When using segments, users can now monitor up to 300 fields for anomalies. The previous limitation was just 1 field.

These improvements help you more easily identify anomalies and more quickly find the root cause.

The chart experience for SQL Rules and Field Quality Rules has been refreshed. The new look and feel allows for more better navigation and easier interpretation of the metrics being displayed by these monitor types.

For Field Quality Rules, specific attention was paid to show the right number of significant figures into the chart tooltips, so the exact details of the rule breach could be easily understood.

The chart experience for Dimension Tracking monitors and incidents has been refreshed. The new look and feel allows for more better navigation and easier interpretation of the metrics being displayed by Dimension Tracking.

All email notifications have gone through a formatting refresh to make them more:

• Interpretable: fewer words, clearer word choice, and more intuitive placement of links
• To-the-point: anomaly or breach information is conveyed sooner, often directly in the subject line
• Impactful: parameterized values from SQL rules are now formatted more clearly, allowing you to clearly convey breached row information into the email

When a user opens a PR, they will now receive a message from MC bot that displays an impact analysis of the PR, where we show a summary of directly impacted models, downstream impacted models, and impacted BI reports. Impacted key assets will show stars next to them. Users can expand to see full list as well as click into MC UI from any of the listed assets.

When logging in at https://getmontecarlo.com/signin, users now see a single field to input their email or account identifier. The app then serves the user the appropriate SSO or password login experience.

This avoids a common issue where users would attempt to log in with a password when SSO had been activated for their account.

Three UI/UX changes have improved user's ability to navigate and interact with Incidents that have associated Jira issues. Users can now:

• Filter the Incident feed for just Incidents with an associated Jira issue
• See the Jira issue from the Incident card on Incident feed
• See the owner and status of the Jira issue from Incident IQ

Inactive Monitors to their channels in Microsoft Teams. Previously, just Slack and Email were supported.

For breached SQL rules, users are now not limited to 500 rows cap when trying to download breached rows. Instead, users can go to the breached rows tab and click on "Run Query and Download CSV" to run the SQL rule live and download up to 10k rows breached.

We previously required customers to have dbt integration before setting up Github integration, to allow mapping from pull requests to models to tables. Now, dbt integration is no longer a prerequisite. All customers that use Github can set up the integration. Customers without dbt integration will still see the most recent PRs in IIQ before the incidents, with the limitation that they will not be able to filter for PRs based on tables or see PRs mapped to the asset page.