Schedule related checks Package

Check if the current UTC date is disallowed by the unique string array disallowed_dates. For example: ["2026-12-31", "from:2026-12-19 to:2026-12-31", "-12-31", "from:-12-20 to:*-01-06"]. Only the year may be . Ranges must use exact lowercase from:X to:Y syntax with one space; surrounding or extra whitespace, alternate order, and case variants are invalid. Concrete range ends must be later than their starts, and both endpoints are included. A later wildcard month/day end stays in one year; an earlier end wraps into the next year. Wildcard ranges use the effective UTC date, including config.policy.when_ns overrides. An early-January date uses the occurrence begun in the prior December. Mixed concrete/wildcard endpoints, equal wildcard endpoints, and -02-29 are invalid. Concrete February 29 is valid only in an explicit leap year. The list is empty by default. This check runs only for a "release" or "production" pipeline, as determined by pipeline_intention.

Solution: Try again on a different day.

Confirm schedule rule data keys use the expected formats. disallowed_dates must be a unique array of strings; see Date Restriction for supported date and range formats. disallowed_weekdays remains a unique array of weekday names.

Solution: If provided, ensure the rule data is in the expected format.

Check if the current weekday is allowed based on the rule data value from the key disallowed_weekdays. By default, the list is empty in which case any weekday is allowed. This check is enforced only for a "release" or "production" pipeline, as determined by the value of the pipeline_intention rule data.

Solution: Try again on a different weekday.