Scenario Health Report · Synthetic preview
What a Scenario Health Report could look like
The Scenario Health Report is a planned product on the ScenarioTrace reliability roadmap. Below is a working prototype rendered from example data so you can see the shape of the report. It uses derived signals, not raw payloads. You can also paste your own derived JSON or fill in a guided form — client-side only, with no data stored or sent.
This is a synthetic preview of a planned product. The Scenario Health Report is planned / prototype — it is not a live paid feature. No Make API connection in this demo — every number below is computed from hand-written example inputs by the pure scoring engine.
- Uses derived signals, not raw payloads — no logs, IDs, or secrets are involved.
- Advisory score, not a guarantee — it does not catch every failure.
- Nothing is fetched, stored, or sent; this page runs entirely on example data.
Three client-side ways to try it — pick one. Everything runs in your browser: no Make API connection, and no data is stored or sent.
Try an example scenario:
Scenario Health Score
A weighted blend of eight reliability dimensions. Higher is healthier. This is an advisory score, not a guarantee.
Top risks
- Operations or credit usage spiked
Category scores
Data availability & confidence
Confidence reflects how much (synthetic) input was available. Missing inputs lower confidence rather than being scored as healthy.
- ✓Blueprint export
- ✓Execution logs
- ✓Scenario outputs
- ✓Module operations
- ✓Pattern signatures
- •Window: 30 days
Prioritized findings (1)
Operations or credit usage spiked
P2 · Medium- Evidence
- operations/credits delta bucket is increased_major vs. baseline
- Likely cause
- A loop/pagination change or larger inputs increased module operations
- Recommended fix
- Review pagination limits and array/iterator sizing to control cost
confidence: mediumsources: execution_logs
Fix checklist & recommendations
Do this first
Review pagination limits and array/iterator sizing to control cost
- 1Review pagination limits and array/iterator sizing to control cost
Recommendations are advisory and derived from example signals. Some steps need a review inside the Make editor or business validation before applying.
Disclaimers
- This score is advisory and not a guarantee of correctness.
- Findings are limited by the data provided (logs, blueprint, outputs).
- No raw logs or payloads are stored; evidence is derived and bucketed.
Export or copy this report
Client-side export — nothing is uploaded, stored, or sent. Derived / synthetic data only (no raw Make logs, IDs, or secrets). Each export includes the advisory disclaimer.
Copy to clipboard
Download a file
Preview the client-safe summary
Scenario Health Report — synthetic / manual preview (derived data only)
Score: 95/100 · Grade A · Risk: low · Confidence: high
Top risks:
- Operations or credit usage spiked
Findings:
[P2] Operations or credit usage spiked
Likely cause: A loop/pagination change or larger inputs increased module operations
Recommended fix: Review pagination limits and array/iterator sizing to control cost
Quick recommendation: Review pagination limits and array/iterator sizing to control cost
Disclaimers:
- This score is advisory and not a guarantee of correctness.
- Findings are limited by the data provided (logs, blueprint, outputs).
- No raw logs or payloads are stored; evidence is derived and bucketed.
Generated client-side from derived / synthetic input. No raw Make logs, PII, or secrets are included. Nothing was uploaded, stored, or sent. Advisory only — not a guarantee.Import your own derived JSON
Paste a derived / bucketed health-score input (the same de-identified buckets and flags the sample scenarios use) to render a report. This runs entirely in your browser.
Before you paste
- Do not paste raw Make logs, payloads, IDs, emails, tokens, or secrets — they are rejected, not stored.
- Use derived/bucketed JSON only (buckets, ratios, and boolean flags).
- This prototype does not store or send data — no data is stored or sent.
- No Make API connection is used; nothing leaves your browser.
Fill in a guided form
Describe your scenario with safe, derived signals — no JSON required. Use buckets and yes/no signals only.
How this works
- Use buckets and yes/no signals only — no raw values or identifiers.
- Do not paste raw Make logs — this form never asks for them.
- No Make API connection. No data is stored or sent.
- Advisory score, not a guarantee — missing data lowers confidence.
Data availability
Blueprint summary
Execution summary
Observability & signals
Observed patterns