Skip to main content

Documentation Index

Fetch the complete documentation index at: https://momentic.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

When a CLI run fails, Momentic can classify the result, explain the reasoning, and attach an action that downstream workflows use for triage. Classification turns raw failure output into a category such as application change, test authorship, test setup, infrastructure, Momentic issue, bug, or other.

​
Capabilities

Results classification can use run artifacts such as screenshots, page state, URLs, step descriptions, element-targeting details, error messages, and stack traces, plus evidence from past runs. It is designed to:
  • Distinguish product changes from brittle or outdated test authoring.
  • Separate application bugs from infrastructure, gateway, browser, or external service failures.
  • Identify missing setup such as test data, files, credentials, or shared fixture state.
  • Detect timing races, missing waits, and async producer/consumer mismatches.
  • Notice when an earlier passing step looks like a false positive based on the later evidence.
  • Flag cases where Momentic execution, AI, cache, or recovery behavior appears to be the failure source.
  • Estimate whether the failure is recoverable by an automated follow-up.

​
Actions

Each category has a configured action:
  • Heal writes the classification data needed for the healing agent to pick up the run and attempt a repair. It exits zero when waiting from the CLI.
  • Warn notifies the user through configured notification channels and exits zero when waiting from the CLI.
  • Fail keeps the run blocking and exits with code 1.
You can tune the action for each category in Settings > Classification.

​
Where you see it

The run viewer surfaces results classification in the failure details for a run:
  • Category and reasoning
  • Confidence and recoverability when available
  • Selected post-classification action
  • Error summary and supporting details
Results classification
The CLI also prints classification details when it waits for run completion, so CI output can distinguish blocking failures from runs that were routed to warn or healing behavior.

​
Manual classification override

The AI classification is a starting point. From the run viewer, you can override the category and add a reason when the AI miscategorizes a failure or when you want to attribute a run to a category your team tracks. Manual overrides are visually distinct from AI classifications in the run viewer, and the run keeps both: the AI’s original category is archived as the previous classification when you save your override. The override flows through the same write path as the AI classifier, so it shows up in dashboard filters and metrics.

​
Configuration

Configure results classification in Settings > Classification.