Observe & tune

Observe mode is a dry run: your detection flow runs live against the screen, but every click and key press is suppressed and logged instead of performed. It's the fastest way to find out why a detection isn't doing what you expected, and it's free for every feature, including the Pro ones.

Start an observation

1. Open the Detection viewClick Detection on the left nav rail and pick the macro to watch.
2. Start observingClick Observe (dry run), then Start observing. The flow runs for real; only the actions are held back.
3. Or try a draft straight from the editorWhile building a flow, Try it (dry run) in the graph editor observes your unsaved draft, so you can check a change before committing it.

Read the event timeline

The Event timeline lists everything as it happens: each check, what matched (with its confidence), each transition the flow took, and every action it would have performed. Select an event to see its details, including where on screen the match landed.

If a step never fires, the timeline shows you which side is failing: the target isn't matching (confidence too low, wrong region) or the transition condition isn't passing.

Tune until it's reliable

• Confidence too strict or too loose? Adjust Match confidence on the step and observe again.
• Matching the wrong thing? Limit the step to a screen region, or recapture a tighter target image.
• Flow bouncing between steps? Watch the transitions in the timeline and tighten their conditions.

Observation is also where Free users can preview the Pro perception features: OCR readings and object recognition both run in dry-run mode, so you can see what they'd do before deciding whether to upgrade.

Export a run report

Export report… saves the whole run as a JSON file, handy for comparing two tuning attempts or attaching to a bug report. Save failure snapshots additionally keeps a screenshot from each failed check so you can see what the screen actually looked like.