Answer
Check whether a configuration change was made that now enforces stricter address-format validation — specifically, requiring an exact matching State Code rather than accepting a wildcard ('*') — since a change like this can silently start rejecting addresses that previously passed validation, breaking a scheduled task that depends on all involved addresses validating cleanly. If a previously-stable pick-list scheduled task suddenly starts failing on state/address validation with no application code changes, review recent changes to address-validation/format-enforcement settings before assuming the scheduled task itself is broken.