MSR Maia Fixed Features 2026

INDEX

Version 1.30.0

• 98354 | UI issues resolved in Ask MAIA configuration screen

• 98546 | MAIA email suggestion truncates sentences and duplicates words

• 100449 | Postal code not always enriched during CV parsing without full enrichment configuration

• 103576 | Error when using a multi-select field in Ask MAIA resolved

Version 1.29.1

• 100720 | Ask Maia shows labels instead of API names
• 101145 | Maia skill enrichment aggregate query error resolved

Version 1.28.0

• 95414 | Skill enrichment added too many skills in some cases
• 99212 | Contact Person record types could not be excluded in MAIA Match
• 100621 | Model selection added to Flow component Generate AI Response

Content

Version 1.30.0

98354 | UI issues resolved in Ask MAIA configuration screen

Some display issues could occur in the Ask MAIA configuration screen. The top of the form was not rendered with correct rounded corners and the dividing line extended beyond the form itself. In addition, a scrollbar was missing when adding multiple fields, making it impossible to continue configuring beyond a certain number of fields. The configuration screen now renders correctly and scrolling is possible when multiple fields are added, keeping all settings accessible.

98546 | MAIA email suggestion truncates sentences and duplicates words

When generating email texts via MAIA mail recommendation, short texts could be processed incorrectly. In these situations, part of a sentence was omitted or words were unintentionally duplicated in the generated result. This behaviour occurred particularly with short input texts and led to unclear or incorrect email suggestions for users. Input text is now processed correctly regardless of its length. Sentences are included in full and words are no longer duplicated, resulting in more consistent and usable email suggestions generated by MAIA.

100449 | Postal code not always enriched during CV parsing without full enrichment configuration

When a CV does not contain a postal code, the postal code of the city centre is determined via the Here API. In some scenarios, this enrichment was not performed or not updated. This occurred in the following situations:

• If only postal code enrichment was enabled and no other data enrichment configuration was set up, the candidate's postal code was not filled in.
• If MAIA enrichment records already existed, the postal code was not re-determined when a CV was re-parsed with only a city name.
• When re-parsing a CV after the postal code field had been manually cleared, the postal code was not re-enriched.

Postal code enrichment is now performed consistently:

• Also when only postal code enrichment is configured
• Also when re-parsing a CV
• Also when enrichment data already exists

As a result, the candidate's postal code is correctly filled in as soon as a city name is available, regardless of the existing enrichment configuration.

103576 | Error when using a multi-select field in Ask MAIA resolved

When using Ask MAIA, an error could occur when a multi-select field had been added to the configuration and that field contained no value. This caused the search functionality to stop working and a technical error to be displayed. Ask MAIA now also works correctly when multi-select fields are empty and the error is no longer shown.

Version 1.29.1

100720 | Ask Maia shows labels instead of API names
When object configurations were set via Ask Maia to allow access to a picklist such as status, Maia returned the API names of the picklist values. This has been resolved so that Maia now always returns the labels, making the response clear and understandable for the user.

101145 | Maia skill enrichment aggregate query error resolved
With Maia skill enrichment, it could occur that more than 200 skills were added to a candidate. This caused an aggregate query error when opening the Skills tab. This issue has been resolved.

Version 1.28.0

95414 | Skill enrichment added too many skills in some cases
When enriching skills, it could happen that an unintended large number of skills was added to a person. This has now been improved. As a result, the skill profile of candidates and contacts remains more accurate and better usable.

99212 | Contact Person record types could not be excluded in MAIA Match
In the MAIA Match settings, not all relevant person record types were available for exclusion. In particular, Contact Person record types were missing, which meant they could unintentionally be included in the indexing process. This became more noticeable after the expansion of indexing to more fields than only the latest CV.

The configuration has been updated so that all candidate-related record types, including Contact Person, are now available for exclusion in the MAIA Match settings. In addition, the indexing process now checks in advance whether a person is configured as a candidate. As a result, contact persons that are not intended for matching are no longer indexed.

100621 | Model selection added to Flow component Generate AI Response
The Flow component Generate AI Response has been updated so that the AI model used can be set explicitly. This prevents future model changes from having unexpected impact on existing Flows.

Within Mysolution, Gemini 2.5 Flash is already used by default. This has now also been applied to this Flow component. In addition, an optional model selection has been added, allowing Flows to be tested in a controlled way with new models.

If no model is set or an invalid value is provided, gemini-2.5-flash is used automatically. This ensures that existing Flows continue to function unchanged.

The following values are supported:

• gemini-2.5-flash

• gemini-3-flash-preview

The existing parameter variability has been phased out and no longer has any effect on the execution of the component.