AI-generated Key Takeaways
-
The AdRuleService is associated with various error types related to ad rules, including date, frequency cap, priority, slot, and targeting errors, among others.
-
AdRuleDateError specifically lists errors concerning ad rule start and end dates.
-
Common reasons for AdRuleDateError include start or end dates being in the past, the end date not being after the start date, or the end date being too far in the future.
-
AdRuleDateError inherits from ApiError and includes fields like fieldPath, fieldPathElements, trigger, and errorString.
-
The
reasonfield within AdRuleDateError provides detailed enumeration values for the specific date-related issue.
Lists all errors associated with ad rule start and end dates.
- Namespace
-
https://www.google.com/apis/ads/publisher/v202505
Field
ApiError
(inherited) fieldPath
xsd:
string
The OGNL field path to identify cause of error.
fieldPathElements
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.
AdRuleDateError
reason
Enumerations
-
START_DATE_TIME_IS_IN_PAST - Cannot create a new ad rule with a start date in the past.
-
END_DATE_TIME_IS_IN_PAST - Cannot update an existing ad rule that has already completely passed with a new end date that is still in the past.
-
END_DATE_TIME_NOT_AFTER_START_TIME - End date must be after the start date.
-
END_DATE_TIME_TOO_LATE -
DateTimes after 1 January 2037 are not supported. -
UNKNOWN - The value returned if the actual value is not exposed by the requested API version.
