# MGS Beta v9

## New

**Email Alert on Successful Publishing of Policies** 

To improve communication and ensure that users are promptly informed, we have added an email notification feature. Whenever there is a successful publishing of any methodology on Testnet/Mainnet, an email alert with detailed information will be sent to the user.

**Further Evolution of Policy Comparison (Mass Diff)** 

We have extended our policy comparison functionality to allow for mass-comparison of policies across the entire ecosystem. Users can now search for local policies similar or different to a given policy based on a similarity threshold, without needing to import them into the Guardian instance. This feature enhances the efficiency and breadth of policy analysis.

## Updates

**UI Improvements** 

We have made several enhancements to the user interface, including updates to dialog boxes, notification bars, and login screens. These improvements aim to provide a more cohesive and user-friendly experience.

**Obsolete Banner Display** 

The obsolete banner, which should appear at the top of the page when launching MGS, is now functioning correctly and will be displayed as intended.

**Policies with Tools in Dry Run Mode: Performance Improvement** 

The performance of executing policies with tools referenced in dry run mode has been significantly improved. Users will now experience faster execution speeds when importing and running these policies.

{% hint style="info" %}
For the full changelog and release notes on the open-source Guardian please visit: <https://github.com/hashgraph/guardian/releases>
{% endhint %}

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.guardianservice.app/whats-new/release-notes/beta-releases/mgs-beta-v9.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.