What common mistake do developers make with Job classes, why does the mistake cause problems, and what is the safer approach?

What common mistake do developers make with Job classes, why does the mistake cause problems, and what is the safer approach? One recurring problem with job classes is applying it without understanding the boundary it protects. Assuming a queued job runs exactly once; workers can retry jobs, so external side effects should be made idempotent where possible. In addition, Job classes define work that can be dispatched for background processing. Safer engineering approach: keep the responsibility in the correct layer, use the framework's supported API, validate and authorize inputs, avoid hidden side effects, and verify the behavior with tests.