This is most likely related to how Maia currently works, not something you are doing wrong.

At the moment, Maia cannot modify individual widgets on an existing page. It is mainly designed to generate new overview pages with predefined layouts, not to change specific widget styles inside an already created page.

That is why prompts like “make the save button a primary button” usually do not update the existing button.

So this is not a bug. It is simply a current limitation of Maia, and widget styling on existing pages still needs to be adjusted manually.

If this resolves your question, please mark the answer as accepted.

Hi,

You are not really doing anything wrong here. What you’re seeing is more about the current limitations of Maia in Mendix 11 rather than a mistake in your prompt.

Right now Maia works best for generating new artifacts (for example creating pages, microflows, or snippets based on prompts). It is still quite limited when it comes to modifying existing page widgets or changing styling of specific elements inside an already created page. So prompts like “make the save button a primary button” often fail because Maia cannot reliably identify and update that specific widget in the page structure.

In practice, the way to handle this today is still the normal Studio Pro approach:

1. Open the page in the page editor.
2. Select the Save button.
3. In the Appearance properties, set the style to Primary (or apply the btn-primary Atlas class depending on the widget).

Maia can help generate new pages with predefined layouts and styles, but fine-grained UI edits on existing pages still need to be done manually in the editor.

So this isn’t really a bug in your setup—it’s just that Maia’s page customization capabilities are still evolving and don’t yet support targeted styling updates on existing widgets.

Mendix documentation