pyRevit (pyrevitlabs) errors

4 recurring problems engineers report in pyRevit (pyrevitlabs), ranked by impact.

#136 by errors trackedMCADVerification

Recurring pyRevit (pyrevitlabs) errors, by impact

  1. 1A dry-run agent request to Revit 2024.3 came back 'Revit did not become idle within 30 seconds' with run_id null; a later read-only check matched the earlier fixture state, but local run records and the instance registry had nothing matching. They cannot tell if the request executed and rolled back, was rejected before dispatch, or is still queued, with unsaved work open.MCAD · Agent failure · 1 report74
  2. 2A dry run of LoadFamily returns counts but drops the names of modified and deleted elements, so a reviewer has to make a second call to learn what changed; approval gates exist, but the thing the human approves is too thin to review.Verification · Agent failure · 1 report66
  3. 3Building Revit families through the MCP agent runtime, the skill text said a new family can be saved while the run guard blocks the save; the script only saw Revit's generic "Saving failed", and the guard's block record wasn't tied to it; two skills contradict each other, and each mismatch cost the user a debugging run.Verification · Agent failure · 1 report66
  4. 4pyRevit's agent tooling listed many marked automation operations but could run only 4, each hand-wired with its own C-sharp validator, and operations can now declare typed inputs, with 20 invocable and runs kept query-only.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure4

Engineering tools that address these errors

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.