Why 'X skipped' in bulk actions is useless — and how to fix it

A software developer building a bulk-action feature for a CRUD app found that reporting a single skip count gives operators no actionable information. When multiple rows are skipped, the reasons can vary widely — from permission issues to items already being in the target state — and each reason demands a different follow-up response. The fix involves tracking skip counts per reason rather than as a single total, allowing the system to display messages like '2 not permitted, 1 already stopped' instead of a vague '3 skipped'. A secondary issue discovered was a misleading success toast that reported jobs as stopping while they sat unclaimed in a queue no worker was monitoring. The author argues that a bulk operation returning zero changes should always surface as a warning, even if every skip was technically legitimate.