Schedule Exception Resolver

Worked example

A weekly Monday base schedule generating January 4 and January 11, with January 11 removed as an exclusion and January 20 added as an inclusion, resolves to a final schedule of January 4 and January 20, the base rule's own unaffected date plus the moved replacement, with the excluded date genuinely gone from the result. Add January 11 back in as an inclusion too, alongside its own exclusion, and the exclusion still wins, removing that date from the final schedule regardless of it also appearing on the inclusion list. This precedence, exclusions always winning over inclusions for the exact same date, keeps the resolver's behavior predictable even when the two lists happen to overlap.

Common mistakes

• Adding the same date to both the inclusion and exclusion lists and expecting it to appear in the final schedule. Exclusions always take precedence, so that date is removed either way.
• Assuming an inclusion date has to match the base rule's own pattern. It does not. An inclusion can be any date at all, since it represents a deliberate one-off addition rather than a generated occurrence.

Limitations

Up to 100 inclusions and exclusions are supported together. This does not verify that an inclusion date is otherwise meaningful, such as confirming it does not conflict with some other commitment beyond this specific schedule.