Robinhood applies multiple break rules at the queue level based on shift length, so a single agent in the by-person view can have several rules assigned at once. When multiple rules are attached, it becomes difficult to tell which one would actually fire if a schedule were generated now. The full set of assigned rules can expand into a long list, which obscures the rule that matters for that specific agent.

Ask: a clearer view that filters the assigned rules down to the one (or ones) that would actually apply for a given agent, based on their current working hours and shift length. Rather than surfacing every potential rule, show the rule that schedule generation would select given the agent's shift conditions.

This applies most directly to queues where agents share break rules but have different working hours and shift lengths. Worth extending the same logic to any other scenario where multiple conditional rules resolve down to a subset at generation time.