ERRORGTFS Schedule notice

Two alternative booking-window limits are both set

forbidden_prior_notice_start_day
Severity
ERROR
Files to check
1
Report fields
4
Documentation
Curated

Diagnosis

What this notice means

prior_notice_start_day is present together with prior_notice_duration_max.

Operational effect

Why it matters

The rule expresses the booking window using incompatible alternatives.

Scope

Files to check and report fields

Report fieldTypeMeaning
bookingRuleIdstringThe `booking_rules.booking_rule_id` of the faulty record.
csvRowNumberintegerThe row number of the faulty record.
priorNoticeDurationMaxnumberThe value of the `prior_notice_duration_max` field.
priorNoticeStartDayobjectThe value of the `prior_notice_duration_min` field.

Repair

How to fix it

  1. 1

    Check the actual opening time for bookings.

  2. 2

    Keep the applicable day-based or duration-based limit, clear the incompatible field, and review any dependent time fields.

  3. 3
    Check the result

    After a repair, rebuild the archive and validate it again. Confirm that the affected records are correct and that no new related notices appeared. A reviewed warning or informational notice may remain when it describes intentional, supported data.

Re-check your feed in the browserFree, no upload for a file you pick.

Sources

References