Skip to main content
Version: 3.0 (next)

Explain & fix

Beta, early access on request: click the purple button beside a problem, and Maestro starts a new chat that already holds what you see. It proposes a fix and changes nothing without your yes.

Where
Overview · Execution History · Connections · Store & Forward · Data Explorer
Opens
A new chat, with the question already sent
Changes
Nothing until you say yes
Never
Re-runs or replays something that writes to a device
Beta: early access

Explain & fix is part of Maestro, which is in release 3.0 as Beta and is not turned on by default. To use it, ask MaestroHub for early access: you get a licence that carries Maestro. A system administrator then connects an AI provider under Second Brain → Providers.

When something goes wrong, the page that shows it already knows a lot: which connection, which run, the error and the suggested fix. Explain & fix hands all of that to Maestro, so you don't have to copy ids into a chat or describe the problem again.

Where you find it​

PageWhere the button isLabel
Workspace OverviewEach warning and critical row under Needs attentionExplain & fix
Execution HistoryEach run that failed, or completed with errorsExplain & fix
ConnectionsThe Status cell of a broken connection, and the connection's health cardExplain & fix
Store & ForwardA dead-lettered messageExplain
Data ExplorerThe problems on a topic, under What went wrongExplain
  • Readers too, in Store & Forward. Explain on a dead-lettered message is there for people who may only read Store & Forward.
  • Not on the instance overview. The overview of all workspaces has no Explain & fix; open the workspace and use its own Overview.
The Connections list filtered to a failed PostgreSQL connection, with the purple Explain and fix button in its status columnThe Connections list filtered to a failed PostgreSQL connection, with the purple Explain and fix button in its status column

A failed connection in the Connections list carries Explain & fix

What happens when you click it​

  1. A new chat opens. Each click starts a fresh chat, so one problem never mixes with another.
  2. The question is sent for you. It is built from what the page shows: the ids of the things involved, the error, and the remediation the page suggests.
  3. Maestro looks into it with your permissions, and tells you what went wrong in plain words.
  4. Maestro proposes a fix. It shows a Confirm to proceed card that names the change. Nothing changes until you click Confirm.

On a connection​

The chat that Explain & fix opens on a connection is bound to that connection. A fix Maestro proposes there can change that connection only, not its neighbours, and not the pipelines that use it.

On a failed run​

For a run in Execution History, Maestro reads:

  • The failing node, its error, what it received and the values it used. What a node received is kept only when the pipeline's Execution History Detail is set to Full; see Orchestrate.
  • The connection the node uses, and whether it is healthy.
  • Recent changes to the pipeline.
  • The logs around the failure, only when you may read logs. Today that is System Administrators.

What Maestro will not do​

  • Change anything without your yes. Reading and checking need no confirmation, because they change nothing. Every change waits for Confirm. One read waits too: a search of every workspace's logs, not just this one's.
  • Re-run or replay something that writes to a device. Maestro never repeats a run or a step that writes to a machine. When one should run again, you run it yourself.
  • Do more than you may. Maestro acts as you. If you cannot edit a connection, neither can Maestro when it works for you.

When you don't see the button​

The button is hidden when your licence has no Maestro, or when your role does not include permission to chat with Maestro. See Where Maestro works.