For the first and third, my go-to answer is that agents cannot handle all of the route paths in the particular planning group. It is not sufficient for an agent to handle some, they have to be capable of handling all of the route paths that are configured. If there is divergence, then it could be planning group config issues, route path config issues (should always use search functionality to add to ensure it has real historic load versus ad hoc creation), queue/skill deletions/additions, forecasts that are based on older/prior planning group configurations and/or user capabilities (those changes require a new forecast and new schedule to be generated so latest PG config and user capabilities are taken into account). UI and doc note requirement regarding route path handling: Agents must be able to handle all of the route paths in this planning group to be scheduled against any of the route paths in this planning group.

The second one, if 'Minimum Time Between Shifts' is not selected (work plan | General Constraints tab), then I would check what value the 'Minimum Time Between Shift Starts' constraint has. At the Business Unit level you can govern which severity schedule messages should have - the ones related to the above two constraints all look to default to Information level and not Warning or Error level. By chance is the person assigned to a work plan rotations where the issue might exist when they rotate to another work plan?

If nothing obvious, then I would recommend opening a support ticket.

Thanks Jay; I did confirm that the agents can handle all route paths in the planning groups and are showing as members of the planning groups.  I have to Orgs right now running into the same issue, so I may submit a support ticket.