Most job-queue incidents don't start with an outage. They start with one bad job .
A webhook payload with a field your code never expected. A user record that triggers an edge case in your PDF renderer. A third-party API that permanently rejects one specific request. The job fails, gets retried, fails again, and keeps failing, burning worker capacity, spamming your logs, firing the same alert 400 times, and making it hard to see the real problems.
Messages like this are called poison pills : input that can never be processed successfully, no matter how many times you try.…