Processing Queue Insights
Monitor real-time URL processing status and understand queue behavior for optimal automation performance.
The Processing Queue view shows what's happening behind the scenes — which URLs are being generated right now and which are waiting.
Key Columns
| Column | Description |
|---|---|
| URL | Current page being processed |
| Status | Queued, Processing, or Completed |
| Cadence | Refresh interval assigned to that URL |
| Formats | Total formats being generated |
| Next Run | Scheduled time for the next automatic scan |
Queue Status Types
Queued
URL is waiting in line for processing. Position in queue depends on priority level and scheduled cadence time.
Processing
URL is currently being scanned and structured files are being generated. This typically takes 10-30 seconds per URL.
Completed
URL has been successfully processed and all enabled formats have been generated. Next run is scheduled based on cadence.
Failed
URL encountered an error during processing. Geordy will automatically retry in the next cycle. Check error details for troubleshooting.
Queue Behavior
How the Queue Works
- Prioritized URLs always move to the top
High-priority pages are processed first, regardless of when they were added to the queue
- Lower-frequency pages remain queued until their scheduled window
Weekly and Monthly cadence URLs wait for their designated time slot
- Failed items are retried automatically in the next cycle
No manual intervention needed — Geordy handles retries intelligently
Monitoring Queue Performance
Keep an eye on these indicators for optimal queue health:
- Queue size – Should remain relatively stable; consistent growth may indicate cadence adjustments needed
- Processing time – Most URLs complete within 10-30 seconds; longer times may indicate complex pages
- Failed count – Occasional failures are normal; persistent failures require investigation
- Next run times – Should align with your cadence settings (Daily, Weekly, Monthly)
Optimizing Queue Efficiency
Best Practices
- •Prioritize only your most critical pages to avoid queue congestion
- •Use appropriate cadences — not every page needs daily updates
- •Exclude low-value pages (admin, test, archived content) to reduce processing load
- •Monitor failed URLs and address underlying issues (broken pages, access restrictions)
Next Steps
Understand Auto-Refresh & Scheduling→