In Marketing API, v3.2 we introduced a new ads run status where a campaign, ad set, or ad can be set to WITH_ISSUES, if it can't be delivered for any reason.
To incorporate versioning, fields may return different values on read:
| Field | Version 3.2 | Versions Prior to 3.2 |
|---|---|---|
|
|
|
| List of error messages | Error |
|
|
|
|
|
|
Example - v3.2/ad_object_id?fields=effective_status,status,issues_info
{
"effective_status": "WITH_ISSUES",
"status": "PAUSED",
"issues_info": [
{
"level" : 'AD',
"error_code": 1815869,
"error_summary": "Ad post is not available",
"error_message": "The Facebook post associated with your ad is not available. It may have been removed, or you may not have permission to view it." }
],
"id": "<ad_object_id>"
}Example - v3.1/ad_object_id?fields=effective_status,status,issues_info
{
"effective_status": "PAUSED",
"status": "PAUSED",
"id": "<ad_object_id>"
}Example - v3.1/ad_object_id?fields=issues_info
{
"error": {
"message": "(#12) Using new run status WITH_ISSUES and ISSUES_INFO requires version v3.2 or higher",
"type": "OAuthException",
"code": 12,
"fbtrace_id": "<fbtrace_id>"
}
}When an ad object is set to WITH_ISSUES, you can still make regular writes to the object:
WITH_ISSUES.WITH_ISSUES. ISSUES_INFO Structure
ISSUES_INFO contains a list including error_code, some error_summary, error_message, and level to indicate which level the issue occurs. Possible values for level are AD, AD_SET and CAMPAIGN. For example, querying ISSUES_INFO on ad level could return issues occurred on itself and its parents, if there are any.
WITH_ISSUES Status and ISSUES_INFO Relation
Currently, ISSUES_INFO is provided when the current level's effective_status is set to WITH_ISSUES.
For more details, see the Marketing API v3.2 changelog.
TAGS
Sign up for monthly updates from Meta for Developers.