This page is the operational guide to running, watching, and stopping Analyst Report jobs.
Starting a run
The first time you open a property, the workspace shows a setup panel at the top (on the Analyst Report tab):
- (Optional) upload documents — rent roll, OM, P&L. Or click Skip — I'll start without uploads.
- On Review & start, tick Run Financial Pro-Forma automatically when Analyst Report finishes if you want the pro-forma built right after the research.
- Click Run Analyst Report. If documents are still processing, the button reads Queue Analyst Report and the run starts once they're ready.
The setup panel disappears and section cards begin populating in real time.
For a property that's already had a run, you can re-run from the property header with Rerun Analyst Report (full re-run) or from any individual section's page (per-section re-run — see Per-section reruns).
Watching progress
Each section card shows a status pill while an Analyst Report works on it:
- Pending — waiting for earlier sections to finish.
- Analyzing — agent is actively working.
- A green check with the time — finished successfully.
- Stopped — you stopped it. Re-run it from the section's page.
- Paused — waiting for credits. It resumes automatically when you top up.
- Failed — finished with an error. Open the section to re-run it.
Sections that haven't been researched yet show no status pill (some show a Preview tag on preliminary data).
The chat panel stays open during a run: messages you send are held and answered as soon as research finishes.
Queue position
Behind the scenes an Analyst Report is queued — each organization can run up to three property analyses at the same time (Analyst Report and pro-forma runs both count). If you start another while three are running, it waits its turn: under the property address, a status reads Analyst Report queued and how many runs are ahead of it (for example, "2 runs ahead"), and the run starts automatically, in order, when a slot frees up.
If you have a Private Server add-on, your runs execute on compute reserved for your organization. See Private / Dedicated server add-on.
Canceling
There are three ways to stop work:
- Stop one section. Click the stop icon on a section card while it's analyzing, then confirm Stop. The section shows Stopped, and you can re-run it later from its page.
- Stop this property's run. Click Stop Research in the property header. Sections that already finished keep their data.
- Cancel everything in your organization. Cancel All (in the property header while a run is active or queued; on a narrow screen it is under the ⋯ menu at the end of the header's buttons) cancels the queued runs you started and stops every analysis currently running in your organization — on every property, including teammates' runs. Use it only when you mean to stop everything.
A run that's waiting — for your uploads to finish or for a free slot — can be canceled on its own with Cancel in that Analyst Report queued status (or Cancel in the setup panel). Only that property's queued run is canceled; the status then says it was cancelled, until another run starts for that property or you reload or leave the page. If your documents could not be processed at all, the queued run doesn't start, and the status says so.
A run you cancel before it starts isn't charged. If you stop a run that's already underway, the work done before you stopped it — including the sections that finished and keep their data — can still use credits.
What happens to partial data
If a run is canceled or fails mid-way, sections that already completed are kept. Sections in progress are discarded. You can re-run only the failed sections later — see Per-section reruns.
If you run out of credits mid-run, nothing is lost: sections that already started finish, and the rest pause until you top up, then resume automatically.
Common reasons a run is slow
- A rent roll with 1000+ units takes longer to extract.
- A property in a tertiary market with thin data coverage triggers more retries on the units pipeline.
- Documents are still processing — the run is scheduled and starts once they're done.
- Your org is already running three analyses, so this one is queued.
See Why is an Analyst Report slow? for the full diagnostic.