What this is
This page documents the constraints that apply to AI analysis operations across the audit lifecycle: timeouts, credit costs, per-plan limits, and strategies to stay within them. Consulting teams running large or complex engagements should review this page before triggering analysis on data-heavy projects.
Before you start
- Review your current credit balance under your workspace avatar → Account → Credits before starting any analysis-intensive step.
- Understand which steps consume credits: web intelligence, document analysis, full AI analysis, memo generation, report generation, and ROI calculation all cost credits. Discovery questionnaire and client profile do not.
Analysis timeout: 180 seconds
Every AI analysis job has a hard timeout of 180 seconds. If the synthesis does not complete within that window, the job is marked as timed out and no findings are written.
What causes timeouts:
- A very large number of documents (especially large PDFs).
- Long interview transcripts (multiple transcripts each >5,000 words).
- Running analysis with all input types simultaneously on a large project.
Strategies to avoid timeouts:
- Keep individual document size under 10 MB and total document count within plan limits.
- Split long transcripts across multiple interview records (see Interviews).
- If you have a very large evidence corpus, run analysis in phases: first with documents and discovery, review findings, then add interviews and re-run.
Credit consumption by step
| Step | Credit cost |
|---|
| Web intelligence | 50 credits per run |
| Document analysis | ~5 credits per document (varies by size) |
| Full AI analysis | ~20–50 credits per run (varies by input volume) |
| Memo generation | ~10 credits per memo type |
| Final report generation | ~30–60 credits per generation |
| Section regeneration | ~5 credits per section |
| ROI calculations | No additional cost |
| Gamma deck generation | ~15 credits per deck |
Credit costs shown are estimates. The actual cost is displayed in the confirmation dialog before you trigger each operation. Costs may vary as the model pipeline is updated.
Per-plan limits
| Limit | Solo | Team | Enterprise |
|---|
| Documents per project | 10 | 25 | Unlimited |
| Interview records per project | 5 | 20 | Unlimited |
| Opportunities on matrix | 5 | 20 | Unlimited |
| Memo types per project | 2 | All | All |
| Report versions | 1 | 10 | Unlimited |
| Concurrent analysis jobs | 1 | 3 | Unlimited |
| Web intelligence runs per project | Unlimited | Unlimited | Unlimited |
| Bundle export | No | Yes | Yes |
What happens when a job times out
- The job is marked Timed out in the project dashboard.
- No partial findings are written (analysis is atomic, it either completes or does not).
- Credits for timed-out jobs are not automatically refunded. Contact support@auditynow.com if a job timed out due to a platform issue rather than input size.
Common issues
My analysis keeps timing out even with a small project.
Check if there are very large individual documents (over 20 MB). Even a single oversized document can cause a timeout. Remove it, reduce its size, or split it.
I hit the document limit mid-project.
Remove documents that are no longer relevant (earlier drafts, duplicates) before adding new ones. Removed documents are not deleted from your workspace, they are unlinked from the project.
Credits depleted unexpectedly.
Review the Credit history under Account settings. Each operation logs a credit deduction with a timestamp and job type. If you see unexpected charges, contact support.
Concurrent analysis limit reached.
Wait for running jobs to complete. The project dashboard shows active jobs across all projects. On Solo plans, you can only run one job at a time across your entire workspace.
What’s next
Return to the audit lifecycle overview or navigate to the specific step you are working on.
