2026-01-08: Sidekiq queueing apdex SLO violation on memory-bound shard

Sidekiq queueing apdex SLO violation on memory-bound shard (Severity 4)

Problem: Bulk import jobs on the memory-bound Sidekiq shard caused job queues to build up and triggered SLO violation alerts, with some jobs not meeting expected queueing targets.

Impact: Multiple Sidekiq queueing SLO violation alerts fired for jobs routed through the memory-bound shard. Delays mainly affected low-urgency jobs, but queues auto-resolved without ongoing customer impact.

Causes: Bulk import operations by multiple users triggered high volumes of BulkImports::RelationBatchExportWorker jobs, which were intentionally throttled for resource protection. This led to job accumulation and delays on the memory-bound Sidekiq shard.

Response strategy: No manual intervention was needed. The queues cleared automatically, and the incident is being resolved with follow-up actions scheduled to investigate why normal import usage is triggering alerts.

This ticket was created to track INC-6497, by incident.io 🔥