Commands  ›  Clash Manager / Manager  ›  Clash Manager Cycle Through All Results In Order

Clash Manager Cycle Through All Results In Order

Clash Manager / Manager writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document; ≥ 1 clash in staging DB matching state filter.

After it runs

Active view set to a 3D view with section box around the next pair.

When to use this

Don't use this when

Bulk export — use the Export commands.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) state_filter = state filter ?? "active". If "active" yields zero rows, fall back to "new".
2) Snapshot the id list; if the current process-scoped cursor refers to an id not in this list (or reset=true), reset cursor to 0 and set wrapped=true.
3) Pick clash at cursor; increment cursor (wraps at end, emits wrapped=true on wrap).
4) Resolve pair in doc; WireError if missing.
5) CycleViewToNextClashResult.ZoomTo(uidoc, [a,b], margin_ft).
6) Emit { clash_id, index, total, wrapped, view_id }.

What you'll see in the chat

on start
Advancing QA clash cursor…
thinking
Listing clashes matching state filter…
Zooming to next pair…
on success
Cycled to clash {clash_id} (index {index} / {total}).
on failure
Cycle failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/clash_manager_cycle_through_all_results_in_order
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashmanagercyclethroughallresultsinorder · cycle through clashes · qa next clash

PillarClash Manager / Manager