Commands  ›  Clash Manager / Solver  ›  Clash Solver Stamp Error And Error Type On Element

Clash Solver Stamp Error And Error Type On Element

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

Coming soon

Before you run this

Active document; target element resolvable; shared params bound to its category.

After it runs

Shared params written inside one Transaction; WireError on missing-binding / read-only.

When to use this

Don't use this when

Read-only queries — use the QA Manager dashboard.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) element unique id (Bot) OR single active selection (Human) must resolve to an Element; WireError if not.
2) error type must be one of StampClashFixReasonOnElement.Types; WireError otherwise.
3) message required, non-empty.
4) Open Transaction "ClashSolver::Stamp"; call StampClashFixReasonOnElement.Stamp(); commit.
5) On success: CentralWarningLogger.LogWarning + tracker.SetOutput(stamped=true).
6) On failure: stamp returns false → WireError already fired inside the service; tracker.SetOutput(stamped=false).

What you'll see in the chat

on start
Stamping element with solver error…
thinking
Resolving target element…
Validating error type against Types taxonomy…
on success
Stamped {errorType} on element {elementId}.
on failure
Stamp 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_solver_stamp_error_and_error_type_on_element
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashsolverstamperroranderrortypeonelement

PillarClash Manager / Solver