Commands › › Error Manager Run Error Check
Error Manager Run Error Check
Coming soon
Before you run this
Active document should be saved so .mepbridge/qa/results.xml can be written beside the RVT. Shared parameter file must be writable when first binding Error / Error Type.
After it runs
results.xml is refreshed (or an error JSON is stored in LastQueryResult).
When to use this
- User or AI triggers a full QA sweep before coordination review.
Don't use this when
Editing rule JSON (use dedicated authoring flows) or manipulating individual clash rows in the navigator.
Inputs
| Name | Kind | Type | Required | Default | Description |
|---|---|---|---|---|---|
ruleSetName |
config | string |
no | — | Optional rule set name (without .json) from project or user RuleSets folder |
Returns
| Name | Type | Description |
|---|---|---|
Result | JSON | Summary counts and output path |
What you'll see in the chat
on start
Running Error Manager checks…
Starting QA rule sweep for this model…
Starting QA rule sweep for this model…
thinking
Ensuring Error / Error Type shared parameters are bound…
Loading the requested rule set (or all discoverable rules)…
Executing rules and aggregating findings…
Writing QA results to results.xml…
Loading the requested rule set (or all discoverable rules)…
Executing rules and aggregating findings…
Writing QA results to results.xml…
on success
Error check finished — {count} findings written to QA XML.
on failure
Error Manager run 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/error_manager_run_error_check- Request body schema (from
[RestApiParam]) - Response schema (from
[RestApiResponse]) - curl / JS / Python code examples
Keywords & intent patterns
run error check · check errors · QA check · run QA · error manager
Related
| Pillar |
|---|