Job Is Marked as Active but Never Processes in Production

[srosama]

Description
We have encountered an issue where a job’s status is set to “Active,” but it never actually begins processing. This behavior primarily occurs in our production environment. In non-production environments (e.g., local development or staging), the job processes without any issues.

// Minimal reproducible code snippet
async function processJob() {
  try {
    const job = await queue.add({ data: 'example' });
    console.log('Job status:', job.getState()); 
    // Expected: "waiting" -> "active" -> "completed" or "failed"
    // Actual: "active" remains stuck, never proceeds till it get stalled *there are nothing wrong with the code 
  } catch (error) {
    console.error('Error creating the job:', error);
  }
}

Expected Behavior
Once queued, the job transitions from waiting to active, processes successfully, and finally moves to a completed or failed state.

Actual Behavior
In production, the job stays stuck in the active state and does not process or produce any output.

Has anyone experienced a similar issue in their production environment?
Are there any recommended configurations or known bugs in the job queue library that might cause a job to remain in an “Active” state indefinitely?
Is there any additional logging or debug information we can enable to diagnose the root cause?