Key Highlights
Summary
Recurring route generation has been optimized to improve performance, scalability, and system stability. The previous sequential processing approach has been enhanced with batch processing and bulk data handling to reduce execution time and system load for large tenants.
What's New?
Recurring runs are now processed in configurable batch sizes instead of sequential execution.
The system introduces controlled concurrency to safely process multiple runs in parallel without overloading services.
Bulk data fetching replaces repeated per-run queries:
• Associations are fetched in bulk across recurring runs
• Runs are retrieved using grouped queries
• Exclusions are processed in bulk
• Itineraries are fetched once per batch and grouped in-memory
Run creation is now executed in batches instead of per run/per date.
Database calls and network overhead are significantly reduced through grouped operations.
Value Delivered
This enhancement improves scalability and reduces system load by minimizing database round-trip and optimizing execution flow. Dispatchers and operations teams benefit from faster recurring route generation and improved system reliability, especially for large datasets.