sincecutoff.com
← all changes

eas workflow:insights:maestro reports Maestro test insights

Introduced 2026-09-11 · score 0.91

HOW TO USE IT

To review Maestro results for a time range, run `eas workflow:insights:maestro` for the overview or add `--flow <flow-path>` for one flow’s history. Use `--json` for script output.

eas workflow:insights:maestro [--days <N> | --start <ISO-date> | --end <ISO-date>]
eas workflow:insights:maestro --flow <flow-path> [--days <N> | --start <ISO-date> | --end <ISO-date>] [--limit <N>]
eas workflow:insights:maestro --json [--days <N> | --start <ISO-date> | --end <ISO-date>]

WHY THIS HELPS

Review Maestro test pass and flake rates, per-flow results, and run history for a time range.

REQUIREMENTS AND LIMITATIONS

  • Version: v24.2.0
  • --days <N>: Show the last N days; defaults to 7, minimum 1. Mutually exclusive with `--start` and `--end`.
  • --start <ISO-date>: Start of the insights time range. Mutually exclusive with `--days`.
  • --end <ISO-date>: End of the insights time range. Mutually exclusive with `--days`.
  • --flow <flow-path>: Show one flow’s history by flow path. Cannot be combined with `--status`, `--tag`, `--search`, `--sort`, or `--sort-direction`.
  • --limit <N>: Number of flows to list or recent runs with `--flow`; defaults to 50 and is capped at 100.
  • --json: Enable JSON output; non-JSON messages go to stderr. Implies `--non-interactive`.
  • --project-id <value>: EAS project ID; defaults to the current directory’s project ID.
  • Prerequisite: The command requires a logged-in EAS context and project context; `--project-id` can override the current directory’s project ID.
  • Prerequisite: Maestro insights are subject to plan availability and time-span limits; the CLI handles plan-gate errors.
  • Insights are displayed for a time range; exact range argument syntax is not stated.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card