What to give FixScenario, and how to read what comes back.

Only the first item is required. Each extra one narrows the diagnosis, and the page tells you what a missing piece costs you before you run.

• The error message, copied from the Make execution log. Raw is better than summarised — the module number and bundle index matter.
• The blueprint (Scenario → Export blueprint). This is what lets FixScenario see the modules around the failure instead of guessing from the text.
• Execution data for the failed run, if you can export it. This is what turns a likely cause into a confirmed one.
• Context: which module you suspect, when it last worked, what you changed since.

A Make blueprint contains connection references, and can contain tokens and keys depending on how the scenario was built. FixScenario strips those before the blueprint is analysed — the diagnosis never needs them, only the shape of the scenario.

The details of what is stripped, what is stored and for how long are on the security page.

Root cause, with a confidence level

Confirmed means the execution data shows it directly. Likely means the blueprint supports it but nothing in the data proves it. A confirmed observation is not a verified repair. Test any proposed change in Make.

Evidence

Every claim points at the field, the bundle or the module it came from. If a line has no evidence behind it, it is stated as an inference, not as a fact.

What to change

The current mapping and the corrected one, side by side. This is the part you copy.

Verify and prevent

What you should see once the fix is in, and what to change so the same failure does not come back after the next edit upstream.

If several causes remain compatible with what you gave it, FixScenario says so and lists what it ruled out, rather than picking the most plausible one and sounding certain. It then names the one piece of missing information that would settle it.

Guessing here would cost you more time than saying nothing: you would go and change a field that was never the problem.

• It does not connect to your Make account and does not edit your scenarios. You apply the fix yourself.
• It diagnoses one failure at a time. It is not a monitoring tool.
• It reasons about the scenario you send. A failure caused by something outside it — a change in a third-party API, a permission revoked in another product — can often be identified, but not always confirmed.