Diagnosis
What this notice means
prior_notice_duration_min is greater than prior_notice_duration_max.
Operational effect
Why it matters
No booking can satisfy both limits as written.
Scope
Files to check and report fields
| Report field | Type | Meaning |
|---|---|---|
bookingRuleId | string | The `booking_rules.booking_rule_id` of the faulty record. |
csvRowNumber | integer | The row number of the faulty record. |
priorNoticeDurationMax | number | The value of the `prior_notice_duration_max` field. |
priorNoticeDurationMin | number | The value of the `prior_notice_duration_min` field. |
Repair
How to fix it
- 1
Compare both durations with the real booking policy and confirm their units.
- 2
Correct the mistaken limit so the minimum is no greater than the maximum; do not swap values unless that reflects the policy.
- 3Check 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