The work that most deserves automating is the work nobody wants to sit and watch: overnight exports, weekly model audits, repeated cleanup before an issue. Nexar Docs registers these as Windows scheduled tasks with a queue and a run history.
A checks job runs a saved Data Standards ruleset, with Model Health optionally alongside. Scheduled runs default to a full rather than sampled analysis, because a sampled run is not comparable with a full desktop run and mixing the two breaks the trend line. Nobody is waiting on a scheduled job, so full is usually the right choice.
Batch mode audits a list of models by opening, auditing and closing each one inside a single Revit session, which is substantially faster than starting a session per model.
A job runs against a local path, a network path, or an Autodesk Construction Cloud model chosen through the ACC browser. Cloud access uses a per-user browser sign-in, with the refresh token stored encrypted for the current Windows user so scheduled jobs keep working.
Output can be written into timestamped folders, or flat into a fixed path when a downstream tool is watching that location.
Anything left blank in a job falls back to the preferences of whoever runs it, which means the same job can produce different results depending on the machine. Settings are pinned to the job so a scheduled run is reproducible.
Yes. Jobs are registered as Windows scheduled tasks with a queue and a run history, and run unattended. The machine must be signed in and the configured Revit version installed.
Yes. Batch mode opens, audits and closes each model in a list inside a single Revit session, which is substantially faster than one session per model.
Yes. A job can target an ACC model chosen through the ACC browser, using a per-user browser sign-in with the refresh token stored encrypted for the current Windows user.