The forecast could not be retrieved due to a server side
connection problem. Please try again soon.
INTERNAL_ERROR
There was an unexpected internal error.
NO_FORECAST_YET
The forecast could not be retrieved because there is not
enough forecasting data available yet. It may take up to one week before
enough data is available.
NOT_ENOUGH_INVENTORY
There's not enough inventory for the requested reservation.
SUCCESS
No error from forecast.
ZERO_LENGTH_RESERVATION
The requested reservation is of zero length. No forecast is returned.
EXCEEDED_QUOTA
The number of requests made per second is too high and has exceeded the
allowable limit. The recommended approach to handle this error is to wait
about 5 seconds and then retry the request. Note that this does not
guarantee the request will succeed. If it fails again, try increasing the
wait time.
Another way to mitigate this error is to limit requests to 2 per second.
Once again this does not guarantee that every request will succeed, but
may help reduce the number of times you receive this error.
OUTSIDE_AVAILABLE_DATE_RANGE
The request falls outside the date range of the available data.
UNKNOWN
The value returned if the actual value is not exposed by the requested API version.
[[["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-13 UTC."],[],[],null,["# enum ForecastError.Reason (v202508)\n\n**Service** \n[AdjustmentService](/ad-manager/api/reference/v202508/AdjustmentService.ForecastError.Reason) [ForecastService](/ad-manager/api/reference/v202508/ForecastService.ForecastError.Reason) [LineItemService](/ad-manager/api/reference/v202508/LineItemService.ForecastError.Reason) [LineItemTemplateService](/ad-manager/api/reference/v202508/LineItemTemplateService.ForecastError.Reason) [OrderService](/ad-manager/api/reference/v202508/OrderService.ForecastError.Reason) [ProposalLineItemService](/ad-manager/api/reference/v202508/ProposalLineItemService.ForecastError.Reason) **ProposalService** **Dependencies** \n[ForecastError](/ad-manager/api/reference/v202508/ProposalService.ForecastError) \n▼\n**ForecastError.Reason**\n\nReason why a forecast could not be retrieved.\n\n*** ** * ** ***\n\nNamespace\n:\n `https://www.google.com/apis/ads/publisher/v202508`\n\n| Enumeration | Description |\n|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `SERVER_NOT_AVAILABLE` | The forecast could not be retrieved due to a server side connection problem. Please try again soon. |\n| `INTERNAL_ERROR` | There was an unexpected internal error. |\n| `NO_FORECAST_YET` | The forecast could not be retrieved because there is not enough forecasting data available yet. It may take up to one week before enough data is available. |\n| `NOT_ENOUGH_INVENTORY` | There's not enough inventory for the requested reservation. |\n| `SUCCESS` | No error from forecast. |\n| `ZERO_LENGTH_RESERVATION` | The requested reservation is of zero length. No forecast is returned. |\n| `EXCEEDED_QUOTA` | The number of requests made per second is too high and has exceeded the allowable limit. The recommended approach to handle this error is to wait about 5 seconds and then retry the request. Note that this does not guarantee the request will succeed. If it fails again, try increasing the wait time. Another way to mitigate this error is to limit requests to 2 per second. Once again this does not guarantee that every request will succeed, but may help reduce the number of times you receive this error. |\n| `OUTSIDE_AVAILABLE_DATE_RANGE` | The request falls outside the date range of the available data. |\n| `UNKNOWN` | The value returned if the actual value is not exposed by the requested API version. |"]]
