Assuming jobs run exactly once is a common systems mistake that surfaces only under pressure.
Naming the pitfall early helps you design tests, reviews, and safer boundaries. Connect the idea to a realistic coding decision so recall is easier when solving similar questions.