Skip to main content

Tasks & runs

Almost nothing in Structured makes you wait. Checks, comparisons, audits, uploads and agent tasks all run in the background while you keep reviewing - which raises the obvious question of where you watch them.

The tasks tray​

The tray is the answer. Click Tasks in the top-right corner, on any page. It lists everything running now and everything that finished in the last 48 hours, with a status and, where we can tell, how much longer it needs.

What shows up there:

RunStarted by
QA/QC runProject QAQC, or the upload wizard
Checklist (named after it)A checklist or a check you built
Spec auditSpec Audit
Compare versionsCompare Versions
Compare against controlCompare Against Control
Comment closureComment Closure
Shop drawing reviewShop Drawing Review
Code reviewA code-compliance check
Code ingestionUploading a book to the code library
Document processingAny upload. Reading is included, at no charge

Clicking a finished run takes you to its results. View all activity at the foot of the tray opens your full history, on the Runs tab of My Dashboard.

Hover a row and click the X to dismiss it from the list. That only tidies the tray - it doesn't cancel the run.

Two states are worth naming:

  • Waiting for documents - a check launched while the project's documents are still processing is parked rather than run. It sits under Running now, shows how long it has waited, and starts automatically once processing finishes.
  • Queued - the run is waiting for a free worker and shows how long it has waited.
The tasks tray open in the top-right corner

Being told instead of watching​

You don't have to keep the tray open:

  • Long runs email you anyway. Any run you started that takes longer than 10 minutes emails you when it finishes, with results attached where there are any. Turn that off in Settings → Preferences (Email me when my long-running tasks finish).
  • For a shorter run, hover it in the tray and click the mail icon (Email me when this finishes).
  • Notifications cover run completions and failures in the app.

When a run is slower than you expected​

Set size is the usual explanation. A check that reasons across every sheet of a 600-page set genuinely takes longer than the same check on a 40-page one. For runs that report progress, the tray's "~N min left" is worked out from that run's own pace. Once a run passes its usual time, the tray reads "finishing up...".

A run that has clearly stalled, or came back with an error, is worth reporting - see Troubleshooting.

Leaving and coming back​

Closing the tab doesn't cancel anything. Runs are server-side: they carry on, land in the tray and the notification bell, and their results are waiting in the project when you come back. The same is true of a long chat job - the thread picks up where it left off.