type DateError (v202502)Stay organized with collectionsSave and categorize content based on your preferences.
Page Summary
DateError is associated with the ForecastService and is inherited from ApiError.
It lists various date-related issues such as dates in the past, invalid date ranges, and unknown errors.
Key fields for this error include fieldPath, fieldPathElements, trigger, errorString (inherited from ApiError), and a specific reason for the date error.
A parsed copy of the field path. For example, the field path "operations[1].operand"
corresponds to this list: {FieldPathElement(field = "operations", index = 1),
FieldPathElement(field = "operand", index = null)}.
trigger
xsd:string
The data that caused the error.
errorString
xsd:string
A simple string representation of the error and reason.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-06 UTC."],[],["The document details error types within the `ForecastService` and `AdjustmentService`, specifically focusing on `DateError`. `DateError` inherits from `ApiError` and includes fields like `fieldPath`, `fieldPathElements`, `trigger`, and `errorString`. `DateError`'s `reason` field indicates the specific date-related problem, with enumerated values such as `DATE_IN_PAST`, `START_DATE_AFTER_END_DATE`, `END_DATE_BEFORE_START_DATE`, `INVALID_DATES` and others. Many error types are available, covering various aspects of ad management.\n"]]
