AI-generated Key Takeaways
- 
          
The document provides a list of possible errors that can occur when creating or modifying account budget proposals.
 - 
          
These errors cover various scenarios, including invalid field masks, immutable or missing required fields, issues with cancelling or removing approved/running budgets, and date/time constraints.
 - 
          
Additional errors relate to budget naming, updates to old or pending budgets, purchase order requirements, and conflicts with existing budgets or billing setups.
 - 
          
Authorization and valid billing setup are also prerequisites, and API creation may be restricted based on user settings.
 
Enum describing possible account budget proposal errors.
| Enums | |
|---|---|
 | 
                Enum unspecified. | 
 | 
                The received error code is not known in this version. | 
 | 
                The field mask must be empty for create/end/remove proposals. | 
 | 
                The field cannot be set because of the proposal type. | 
 | 
                The field is required because of the proposal type. | 
 | 
                Proposals that have been approved cannot be cancelled. | 
 | 
                Budgets that haven't been approved cannot be removed. | 
 | 
                Budgets that are currently running cannot be removed. | 
 | 
                Budgets that haven't been approved cannot be truncated. | 
 | 
                Only budgets that are currently running can be truncated. | 
 | 
                All budgets must have names. | 
 | 
                Expired budgets cannot be edited after a sufficient amount of time has passed. | 
 | 
                It is not permissible a propose a new budget that ends in the past. | 
 | 
                An expired budget cannot be extended to overlap with the running budget. | 
 | 
                A purchase order number is required. | 
 | 
                Budgets that have a pending update cannot be updated. | 
 | 
                Cannot propose more than one budget when the corresponding billing setup hasn't been approved. | 
 | 
                Cannot update the start time of a budget that has already started. | 
 | 
                Cannot update the spending limit of a budget with an amount lower than what has already been spent. | 
 | 
                Cannot propose a budget update without actually changing any fields. | 
 | 
                The end time must come after the start time. | 
 | 
                The budget's date range must fall within the date range of its billing setup. | 
 | 
                The user is not authorized to mutate budgets for the given billing setup. | 
 | 
                Mutates are not allowed for the given billing setup. | 
 | 
                Budget creation failed as it overlaps with a pending budget proposal or an approved budget. | 
 | 
                The control setting in user's payments profile doesn't allow budget creation through API. Log in to Google Ads to create budget. | 
 | 
                Master service agreement has not been signed yet for the Payments Profile. | 
 | 
                Budget mutates are not allowed because the given billing setup is canceled. |