We removed the Redis lock from the track API route, which was inadvertently causing a bottleneck by triggering 429 rate-limit errors across concurrent batch processes. This change improves throughput and allows track requests to proceed without blocking related batches. The system should now handle concurrent ingestion much more gracefully.