Monitoring Processing Status

Zero Docs processes your sources in the background—crawling web pages, ingesting files, and building documentation. The Processing Status console helps you monitor this activity and diagnose issues.

Accessing the Processing Status Console

The Processing Status console appears as a dismissible dialog on the Projects dashboard and Project Overview pages:

┌─────────────────────────────────────────────────────────┐
│ Processing Status                                    ×  │
├─────────────────────────────────────────────────────────┤
│ [log output area]                                       │
│                                                         │
└─────────────────────────────────────────────────────────┘

When processing activity occurs, the console automatically displays recent log entries. You can dismiss it with the × button.

Understanding Processing Logs

Log entries follow this format:

14:19:29 [Crawl] Manual crawl started for Zero Docs - v1

Each entry includes:

• Timestamp: When the event occurred (HH:MM:SS)
• Event type: The operation being performed (e.g., [Crawl], [Ingestion], [Build])
• Description: Details about the specific action
• Context: Which project and version is affected

Common Processing Events

System Status Notifications

In addition to the processing console, system-wide status banners may appear:

┌─────────────────────────────────────────────────────────┐
│ Document ingestion may be slower than usual due to a    │
│ vendor API degradation.                                 │
└─────────────────────────────────────────────────────────┘

These banners notify you of:

• Service degradations: Temporary slowdowns due to vendor issues
• Scheduled maintenance: Planned downtime or updates
• Important announcements: Changes to features or policies

Slow Processing

Problem: Document ingestion or crawling is taking longer than expected.

Common Causes:

• Vendor API degradation (displayed in status banner)
• Large source files requiring extensive processing
• High crawl depth or many linked pages
• Rate limiting on external websites

Solution:

1. Check for system status banners indicating known issues
2. If no system issue is reported, wait for processing to complete—large sources may take several minutes
3. If processing appears stuck for more than 15 minutes, try resetting the affected version's sources and re-running the crawl
4. Contact support if issues persist beyond expected processing times

Processing Errors

Problem: Error events appear in the processing console.

Common Causes:

• Invalid source URLs (404, 403, or network errors)
• Malformed file uploads
• Authentication issues with protected sources
• Quota or rate limit exceeded

Solution:

1. Note the error message and context (project/version)
2. Navigate to the affected version's sources page
3. Review Flagged Sources for any sources marked as problematic
4. Correct or remove invalid sources
5. Re-run processing from the version settings

Monitoring Best Practices

• Check after major changes: After adding new sources or versions, monitor the console to ensure processing completes successfully
• Don't dismiss errors immediately: Read error messages before closing the console—they contain diagnostic information
• Cross-reference with version status: If the console shows activity for a version, check that version's sources page to see updated status

Next Steps

• Review flagged sources if processing errors occur
• Manage version sources to add, edit, or remove content
• Contact support if processing issues persist