c31325e982
This PR fixes flaky test failures in the Instagram webhook specs that were caused by Redis mutex lock conflicts when tests ran in parallel. ### The Problem: The InstagramEventsJob uses a Redis mutex with a key based on sender_id and ig_account_id to prevent race conditions. However, all test factories were using the same hardcoded sender_id: 'Sender-id-1', causing multiple test instances to compete for the same mutex lock when running in parallel. ### The Solution: - Updated all Instagram event factories to generate unique sender IDs using SecureRandom.hex(4) - Modified test stubs and expectations to work with dynamic sender IDs instead of hardcoded values - Ensured each test instance gets its own unique mutex key, eliminating lock contention |
||
|---|---|---|
| .. | ||
| facebook_delivery_job_spec.rb | ||
| facebook_events_job_spec.rb | ||
| instagram_events_job_spec.rb | ||
| line_events_job_spec.rb | ||
| sms_events_job_spec.rb | ||
| telegram_events_job_spec.rb | ||
| twilio_delivery_status_job_spec.rb | ||
| twilio_events_job_spec.rb | ||
| whatsapp_events_job_spec.rb | ||