Agent Platform
Scenarios
Describe a failure or condition once, and Alloy checks your past and new missions for it
Use this page to turn a failure your team debugged once into a check that runs on every new mission.
A scenario is a check you describe in plain language. Alloy runs it on your missions from the past 7 days by default (up to 90 days) and on each new one, and lists the matches. The next person to see the failure starts from a list of every occurrence, not from a raw log. A scenario finds what you describe, nothing more: it does not predict or prevent faults.
When to use scenarios
- Track recurring issues: "motor fault events at high altitude"
- Watch a regression: "battery voltage below 11V during flight", checked on every new firmware's test runs
- Build a dataset: collect every occurrence of a particular event type across your fleet
- Count how often something happens, without searching by hand
Creating a scenario
Ask the agent to create one:
- "Create a scenario to find all emergency stop events"
- "Set up a scenario for navigation errors near waypoints"
- "Watch for times when roll angle exceeded 30 degrees"
The scenario list
The Scenarios page shows all your scenarios in a table:
| Column | What it shows |
|---|---|
| Name | What the scenario is tracking |
| Status | Progress ("Scanned 19 of 39"), Up to date, or Paused ("Paused at 19 of 39" if not finished) |
| Matches | Matches found so far |
| Created | When the scenario was set up |
Each row also has Actions to pause, resume or archive the scenario. To see archived scenarios, open the menu next to Create and choose View Archive.
How checking works
When you create a scenario, Alloy works through your mission library in the background.
- Alloy checks each mission for your pattern
- Progress shows as "Scanned X of Y", where Y is the number of missions to check. When it finishes, the status reads Up to date (Scanned all missions in the new design)
- New missions uploaded after the scenario was created are checked too
- You don't need to re-run anything. A scenario stays active until you pause or archive it
Checking runs in the background. You can keep using Alloy while it runs. Large libraries take longer to check fully.
Viewing matches
Click a scenario to see its matches. Each match is one event, and shows:
- Match reason: a short explanation of why it matched
- Time window: when the event happened
- Mission: which mission it came from
- Images: the most relevant images from the match, when the mission has images
Filtering and sorting matches
- Filter by device, location, date, or any metadata field in your missions
- Combine filters to narrow down to specific conditions
- Sort by Detected At, Start time, Uploaded At, or Mission
For example, if your scenario finds 50 matches across 20 missions, you can filter to see only matches from one device, or sort by start time to see when the pattern occurs most often.
If a match is wrong, open the menu on that match's card and choose Remove match….
How far back to check
The scenario's menu has an Initial scan range, from Previous 7 days to Previous 3 months. It sets how far back Alloy checks earlier missions. It does not filter the matches list, and Alloy always checks new missions.
Editing a scenario
Both the scenario name and definition are editable.
- Name: click the pencil icon next to the scenario name to rename it inline
- Definition: click Edit on the definition to open the agent. Describe how you want to change the pattern and the agent rewrites the definition for you. Depending on the change, Alloy may check your missions again to find new matches
Managing scenarios
From the scenario's menu:
- Pause scanning: stop checking without losing progress or results
- Resume scanning: pick up where you left off
- Archive: remove from the active list while keeping all results
- Unarchive: bring back an archived scenario