raise BullMQ lockDuration to survive long domain jobs
Domain jobs upsert up to 10,000 keywords sequentially (2 DB round-trips
each) plus Google Ads quota-retry backoff, routinely exceeding the 30s
BullMQ default lockDuration. Once the lock expires mid-job, stalled-job
recovery reassigns the job and the original process's later
moveToFinished races the reassignment, surfacing as "could not renew
lock", "Missing key for job ... moveToFinished" and "Lock mismatch"
errors (dozens/week in the Errors-as-Tasks firehose). Raise lockDuration
to 10 minutes on both keyword-planner workers.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011XC3R3yf9u7xnZneEKnU8w
each) plus Google Ads quota-retry backoff, routinely exceeding the 30s
BullMQ default lockDuration. Once the lock expires mid-job, stalled-job
recovery reassigns the job and the original process's later
moveToFinished races the reassignment, surfacing as "could not renew
lock", "Missing key for job ... moveToFinished" and "Lock mismatch"
errors (dozens/week in the Errors-as-Tasks firehose). Raise lockDuration
to 10 minutes on both keyword-planner workers.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011XC3R3yf9u7xnZneEKnU8w