AI-generated Key Takeaways
- 
          OrderError.Reasonprovides the reasons for target errors related to orders.
- 
          There are various specific error reasons listed, such as not being allowed to update canceled, pending approval, or archived orders. 
- 
          Other error reasons involve restrictions on modifying the proposal ID, requirements for primary and secondary users, and rules regarding team associations for orders, advertisers, users, and agencies. 
- 
          An error is also triggered if programmatic info fields are set for a non-programmatic order, and an UNKNOWNvalue is returned for reasons not exposed by the API version.
The reasons for the target error.
- Namespace
- 
               https://www.google.com/apis/ads/publisher/v202508
| Enumeration | Description | 
|---|---|
| UPDATE_CANCELED_ORDER_NOT_ALLOWED | Updating a canceled order is not allowed. | 
| UPDATE_PENDING_APPROVAL_ORDER_NOT_ALLOWED | Updating an order that has its approval pending is not allowed. | 
| UPDATE_ARCHIVED_ORDER_NOT_ALLOWED | Updating an archived order is not allowed. | 
| CANNOT_MODIFY_PROPOSAL_ID | DSM can set the proposal ID only at the time of creation of order. Setting or changing proposal ID at the time of order update is not allowed. | 
| PRIMARY_USER_REQUIRED | Cannot have secondary user without a primary user. | 
| PRIMARY_USER_CANNOT_BE_SECONDARY | Primary user cannot be added as a secondary user too. | 
| ORDER_TEAM_NOT_ASSOCIATED_WITH_ADVERTISER | A team associated with the order must also be associated with the advertiser. | 
| USER_NOT_ON_ORDERS_TEAMS | The user assigned to the order, like salesperson or trafficker, must be on one of the order's teams. | 
| AGENCY_NOT_ON_ORDERS_TEAMS | The agency assigned to the order must belong to one of the order's teams. | 
| INVALID_FIELDS_SET_FOR_NON_PROGRAMMATIC_ORDER | Programmatic info fields should not be set for a non-programmatic order. | 
| UNKNOWN | The value returned if the actual value is not exposed by the requested API version. |