A typical Intel Report run is 5–10 minutes. If yours is taking 20+ minutes, this page walks through the most common reasons and what to do.
1. Documents are still processing
If you start an Intel Report while uploaded documents are still processing, Relm doesn't start the run yet — it schedules it and starts it automatically once every document has finished. Processing a 200-page PDF can take 1–2 minutes on its own.
Check: the Run Intel Report button shows a document count (for example, "2/3 docs") or reads Scheduled — starts after uploads. In the setup panel, the button reads Queue Intel Report.
What to do: keep the property page open — the run starts on its own as soon as processing finishes.
2. Large rent roll
A rent roll with 500+ units takes longer to extract and validate than a 50-unit one. Bigger isn't bad — it's just real work.
Check: the property's expected unit count from Basic Info or the OM.
What to do: wait. If the rent roll is genuinely huge (1000+ units), expect 3–5 minutes for the Units section to settle.
3. Tertiary-market data thinness
Properties in tertiary markets sometimes trigger more retries on listing platforms (which return slower or empty responses) and on the agentic Units pipeline. The crawler retries when it hits a rate-limit or a thin source.
Check: how many of the property's section cards are still Analyzing past 3 minutes.
What to do: for properties you'll research repeatedly in the same submarket, our cache fills in over time and subsequent runs are faster. If a particular section keeps timing out, report the property URL so we can tune the agent.
4. Org-wide queue
Each organization can run up to three property analyses at a time (Intel Report and pro-forma runs both count). If more are running in your org, later ones queue up.
Check: the property header shows Queued (#N) instead of the Run button.
What to do: wait — runs proceed in order and start automatically. If your team is consistently saturating capacity, talk to sales about Enterprise concurrency or a Private Server.
5. Listing platform rate limit
The comps and units agents occasionally hit listing-platform rate limits. We back off and retry. A backoff cycle adds 30–90 seconds.
Check: the section's live progress notes mention a retry.
What to do: wait for the retry, or stop the section and re-run it later when the platform is less hot (re-runs use credits).
6. Anomaly detection re-running
The Units pipeline includes anomaly detection — when the agentic crawler returns a suspicious unit count, it re-attempts the discovery rather than committing the bad number. That's slower but produces better data.
Check: the Units card is still Analyzing after the other sections have finished.
What to do: wait. If the verification keeps failing for a property, report it as a bug so we can dig into that property's data sources.
7. Backend incident
If our agent platform is degraded, all properties in your org will run slowly. We surface this on the Status page.
Check: /status — incidents are posted there.
What to do: wait for the resolution; we'll auto-retry runs once the platform is healthy again.
8. Out of credits
If your balance runs out mid-run, sections that already started finish normally and the rest pause instead of failing.
Check: amber Paused pills on section cards, or a "Paused — out of credits" notice under the property header.
What to do: add credits — the Buy credits link opens the Billing page. Paused sections resume automatically; you don't need to re-run anything.
When to give up and re-run
If a run is past 15 minutes with no progress on any section, it's worth stopping and re-running:
- Click Stop Research in the property header. (Don't use Cancel All — it stops every analysis running in your organization.)
- Wait 30 seconds.
- Start the run again from the property header (Run Intel Report or Rerun Intel Report).
If the second run also stalls, contact support with the property URL.