Page Summary
-
This content provides an enumeration of possible errors that can occur with feeds.
-
The list details various errors related to feed attributes, origins, naming, authentication, business accounts, and location-based feeds.
-
Specific errors highlight constraints on system versus user-generated feeds and limitations on updating or managing feeds with Google origin.
-
Issues like duplicate names, invalid emails, missing OAuth information, and exceeding the attribute limit are also covered.
Enum describing possible feed errors.
| Enums | |
|---|---|
|
The attribute list must be an exact copy of the existing list if the attribute ID's are present. |
|
The names of the FeedAttributes must be unique. |
|
Business account cannot access Business Profile. |
|
A customer cannot have both LOCATION and AFFILIATE_LOCATION feeds. |
|
Cannot specify feed attributes for system feed. |
|
Cannot specify GOOGLE origin for a non-system generated feed. |
|
Cannot specify USER origin for a system generated feed. |
|
Cannot update FeedAttributes on feed with origin GOOGLE. |
|
Feed name matches that of another active Feed. |
|
There is already a feed with the given system feed generation data. |
|
A user can only create and modify feeds with USER origin. |
|
The given ID refers to a removed Feed. Removed Feeds are immutable. |
|
An error occurred accessing Business Profile. |
|
Invalid chain ID provided for affiliate location feed. |
|
Invalid auth token for the given email. |
|
The business account is not valid. |
|
Invalid email specified. |
|
Name of feed is not allowed. |
|
The origin of the feed is not valid for the client. |
|
Feed-based extension is read-only for this extension type. |
|
Missing OAuthInfo. |
|
New FeedAttributes must not affect the unique key. |
|
Too many FeedAttributes for a Feed. |
|
The received error code is not known in this version. |
|
Enum unspecified. |