> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spojit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Suggested fixes

> Miraxa investigates each alert and suggests a fix. Apply it yourself, or let low-risk fixes apply on their own, with Undo.

A monitor can ask Miraxa to look into each alert as it happens. Miraxa investigates, writes up what it found and suggests what to do. When the fix is a change to your workflows, you can apply it from the alert, or let the monitor apply low-risk fixes on its own.

## Suggested next steps

Turn on **Ask Miraxa for suggested next steps** under a monitor's **More options**. Each time the monitor alerts, Miraxa looks into it with read-only access to the whole workspace and writes:

* a **Suggested fix**: what to do, in a few lines;
* **How Miraxa worked it out**: what it checked and found, folded underneath.

While it works, the alert shows *Miraxa is looking into this*. The first alert waits up to two minutes so the suggestion can travel with it to email, Slack and Teams.

Miraxa investigates as the workspace, not as any one person, and can only read. Everyone who can see the alert sees the suggestion; whoever acts on it does so with their own permissions. Suggested next steps use AI credits, and turning them on needs permission to view every workflow, folder and connection in the workspace.

## Apply

When the suggestion is a change Miraxa can make, the alert offers to apply it. There are two kinds.

| Kind | What happens |
| - | - |
| **Apply the proposed change** | A set value swap across one or more workflows, such as a new price or an updated API version. It is applied as a bulk change, so you can review it first with **Review the proposed change**, and undo it from the bulk change's page. |
| **Apply with Miraxa** | Miraxa makes the changes the suggestion describes, using your access, in a chat you can follow and continue. |

Both ask you to confirm first. Applying needs permission to manage monitors; **Apply with Miraxa** also needs permission to use Miraxa's Auto mode.

A notice about something with a future date, such as a price change taking effect next month, offers **Apply now** or **Apply on** that date. You can cancel a scheduled apply until it runs.

### Before you apply

Each suggestion shows its risk (**Low**, **Medium** or **High**) and flags anything to know first:

| Flag | Means |
| - | - |
| **Deletes** | The change removes something. |
| **Changes where data goes** | It changes a destination, such as an address or recipient. |
| **Sends data out** | It would send data outside the workspace. |
| **Changes trigger or approval** | It changes how a workflow starts, or an approval step. |
| **Based on outside text** | The suggestion relies on text from a web page, an API or a broadcast. |
| **Re-runs writes** | It would repeat steps that write to other systems. |
| **Unchecked** | Miraxa could not check the change fully. |

When a suggestion is based on outside text, sends data out, or is unchecked, **Apply with Miraxa** is not offered. Use **Continue in Miraxa** to work through it together instead.

## Auto-apply

**Auto-apply suggested fixes** lets a monitor apply fixes without waiting for someone to press Apply. Choose:

* **Off**: a person presses Apply (the default).
* **Low risk fixes**: an exact value swap in up to three workflows.
* **Low and medium risk fixes**: an exact value swap in up to ten workflows.

A fix Miraxa writes itself, changing settings or steps, waits for someone to press Apply.

High-risk fixes never apply on their own. Nor does anything that changes a trigger or an approval, removes a step, changes where data goes, reaches outside the workspace, or that someone has undone before. The risk is judged from the actual edits, not from Miraxa's description of them.

When a fix applies on its own:

1. Everyone on the alert is told what changed, with an **Undo** button.
2. The monitor watches the next runs of each changed workflow and alerts if they fail.
3. **Undo** puts each workflow back as it was, using the permissions of the person undoing it.

Turning auto-apply on needs permission to manage auto-apply (Owners and Admins by default), and the monitor must have suggested next steps on. It turns off again if you change what the monitor watches. The monitor's page shows whether auto-apply is on, at which level, and who turned it on.

> [card] [Try this on the free plan](https://miraxa.spojit.com/signup)
>
> 500 AI credits and 200 workflow runs a month, no card needed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.