Publishing Failures
This guide helps you resolve publishing errors and handle scenarios where campaigns fail to publish. Learn how to diagnose issues, fix problems, and retry failed publishes.Understanding Publishing Failures
When you publish campaigns, Whathead validates your configuration and sends it to the platform’s API. Failures can occur at different stages:- Validation failures: Issues detected before sending to the platform
- API failures: Platform rejects the campaign during publishing
- Partial failures: Some campaigns succeed while others fail
- Network failures: Connection issues during the publish process
Common Publishing Errors
Validation errors prevent publishing
Validation errors prevent publishing
Problem: The Publish button is disabled or validation errors appear before you can publish.Common Causes:
- Required fields are missing
- Budget below platform minimum
- Invalid targeting configuration
- Hierarchy rules violated
Platform API rejects campaign
Platform API rejects campaign
Problem: Publishing starts but the platform returns an error.Common Causes:
- Platform-specific validation rules not met
- Ad account spending limit reached
- Creative content violates platform policies
- Targeting options not available in your region
Check platform-specific requirements
Review the platform’s documentation for specific rules (see Platform pages)
Some campaigns succeed, others fail (partial failure)
Some campaigns succeed, others fail (partial failure)
Problem: When publishing multiple campaigns, some publish successfully while others fail.What Happens:
- Successful campaigns are created/updated on the platform
- Failed campaigns remain in draft state in Whathead
- You receive a summary showing which campaigns succeeded and which failed
Successful campaigns are not affected when you retry failed ones. You can safely retry without duplicating successful publishes.
Network timeout during publishing
Network timeout during publishing
Problem: Publishing fails due to network connectivity issues or timeout.Common Causes:
- Slow internet connection
- Platform API temporarily unavailable
- Large campaign taking too long to process
- Firewall or proxy interfering with API calls
Authentication expired during publishing
Authentication expired during publishing
Problem: Publishing fails with an authentication or permission error.Common Causes:
- OAuth token expired (typically after 60-90 days)
- Platform permissions were revoked
- Ad account access was removed
- Session timed out
Check ad account access
Confirm you still have access to the ad account in the platform’s native portal
Creative assets fail to upload
Creative assets fail to upload
Problem: Campaign publishes but creative assets (images, videos) fail to upload.Common Causes:
- Asset file size exceeds platform limits
- Asset format not supported by platform
- Asset dimensions don’t meet platform requirements
- Network issues during asset upload
Budget or bid amount rejected
Budget or bid amount rejected
Problem: Platform rejects the campaign due to budget or bid amount issues.Common Causes:
- Budget below platform minimum
- Budget above ad account spending limit
- Bid amount not appropriate for objective
- Currency mismatch
- Meta: $1/day minimum
- TikTok: $20/day minimum
- Snapchat: $5/day minimum
- Google: $10/day minimum
Targeting configuration rejected
Targeting configuration rejected
Problem: Platform rejects the campaign due to targeting issues.Common Causes:
- Targeting options not available in your region
- Audience size too small or too large
- Conflicting targeting criteria
- Special ad category restrictions (Meta)
Retry Workflow
When campaigns fail to publish, follow this workflow to resolve and retry:Review the failure summary
After a failed publish, Whathead shows a summary of what succeeded and what failed
Read error messages
Each failed campaign includes an error message from the platform explaining why it failed
Select failed campaigns
In the canvas, select only the campaigns that failed (successful ones don’t need to be republished)
When you retry publishing, Whathead remembers which campaigns already succeeded and won’t duplicate them. Only failed campaigns are retried.
Handling Partial Success Scenarios
Scenario 1: Multiple Campaigns, Some Fail
What Happens:- You publish 10 campaigns
- 7 succeed, 3 fail
- The 7 successful campaigns are live on the platform
- The 3 failed campaigns remain in draft state
- Don’t panic - the successful campaigns are fine
- Review error messages for the 3 failed campaigns
- Fix the issues in those 3 campaigns
- Publish only those 3 campaigns again
- All 10 campaigns are now live
Scenario 2: Campaign Succeeds, Ad Sets Fail
What Happens:- Campaign is created on the platform
- Some ad sets fail to create
- Campaign exists but is incomplete
- The campaign now has an existing ID
- Fix the ad set issues
- Publish again - the campaign will be updated (not duplicated)
- Failed ad sets will be created under the existing campaign
Scenario 3: Everything Succeeds Except One Ad
What Happens:- Campaign and ad sets are created
- One ad fails (e.g., creative asset issue)
- Campaign structure exists but is missing one ad
- Fix the ad that failed (e.g., replace the creative asset)
- Publish again
- The campaign and ad sets will be skipped (no changes)
- Only the failed ad will be created
Platform-Specific Publishing Issues
- Meta
- TikTok
- Snapchat
- Google
Common Meta Publishing Failures
Special Ad Categories:- If your campaign is about housing, employment, or credit, you must declare it
- Targeting is restricted for special ad categories
- Failure to declare can result in ad rejection
- Meta reviews creative content for policy compliance
- Ads may be rejected after publishing if they violate policies
- Check Meta’s advertising policies before publishing
- Minimum $1/day per ad set
- Account spending limits can block publishing
- Payment method issues prevent campaign activation
When to Contact Support
Contact Whathead support if:- Error messages are unclear or don’t provide actionable information
- Publishing fails repeatedly with the same error after fixing the issue
- You receive an error that seems like a bug rather than a configuration issue
- Platform API returns unexpected errors
- You need help understanding platform-specific requirements