Troubleshooting Campaign Publishing Errors
Last updated: April 18, 2026
When a campaign fails to publish, Wevion provides detailed error information to help you fix the issue quickly. This article covers the most common publishing errors and how to resolve them.
Prerequisites
Understanding of the Campaign Launcher Campaign Launcher Overview — How It Works
An attempted campaign launch that resulted in an error
How It Works
Campaign publishing goes through multiple validation layers:
Frontend validation — Wevion checks your configuration before sending it to Meta. These errors appear instantly as red indicators on the grid.
Backend validation — The server verifies your token, ad account, and required settings.
Meta API validation — Meta's API accepts or rejects each element (campaign, ad set, ad). If Meta returns an error, Wevion captures the user-friendly message.
Automatic rollback — If any step fails after partial creation, Wevion deletes all partially created resources to keep your account clean.
All errors are recorded in the progress tracker with the original error message from Meta when available.
Common Validation Errors (Pre-Publish)
These errors appear in the Campaign Launcher grid before you publish:
Missing Required Fields
ErrorFix | |
Meta profile not selected | Select a Meta Profile (token) at the top of the page |
Campaign name required | Enter a campaign name |
Objective required | Select a campaign objective |
Ad account required | Select an ad account |
Fan page required | Select a fan page for the ad set |
Budget required | Enter a daily budget (minimum €1.00) |
Budget Errors
ErrorFix | |
Budget must be at least €1.00 | Increase your daily budget to at least 1.00 |
Bid amount required | Enter a bid amount when using Bid Cap, Cost Cap, or Min ROAS strategy |
ABO ad set budget required | In ABO mode, each ad set needs its own daily budget |
Pixel and Conversion Errors
ErrorFix | |
Pixel required | Select a pixel. Required for Sales, Leads, and Traffic (with conversion goals) |
Custom event type required | Select a conversion event (e.g., Purchase, Lead). Required when optimizing for Offsite Conversions, Value, or Quality Lead |
Invalid optimization goal | Your optimization goal doesn't match the selected objective. See [ART-203] for valid combinations |
Creative Errors
ErrorFix | |
Image or video required | Upload at least one image or video for each ad (unless using Existing Post or Catalog) |
Primary text required | Enter the main ad copy |
Headline required | Enter a headline for the ad |
Landing page URL required | Enter a destination URL. Required for conversion-based optimization goals |
Post ID required | When using Existing Post, enter the post ID |
Targeting Errors
ErrorFix | |
DSA Beneficiary required | Fill in the DSA beneficiary field — required when targeting EU countries [See: ART-209] |
DSA Payor required | Fill in the DSA payor field — required when targeting EU countries |
Min age must be 18+ for special categories | Special Ad Categories (financial products, employment, housing, political issues) require minimum age of 18 |
End date must be after start date | Your schedule end date is before the start date |
Ad Type Specific Errors
ErrorFix | |
Catalog only valid with Sales objective | Catalog (DPA) ads require the Sales objective |
App ID required | App Install ads require an App ID |
App Store URL required | App Install ads require an App Store URL |
Target language required | Multi-language ads need a primary target language |
Secondary language required | Multi-language ads need at least one secondary language |
Common Meta API Errors (During Publish)
These errors come from Meta's API during the actual publishing process:
Token and Permission Errors
ErrorCauseFix | ||
Token expired | Your Meta access token has expired | Reconnect your Meta account from Settings. [See: ART-224] |
Invalid token | Token is no longer valid | Same as above — reconnect your Meta account |
Permission denied | Your token doesn't have the required permissions for this ad account | Reassign the ad account or reconnect with full permissions. [See: ART-222] |
Creative Rejection
ErrorCauseFix | ||
Ad creative rejected | Meta's review system flagged your creative | Review Meta's advertising policies. Common issues: misleading claims, prohibited content, personal attributes targeting |
Image too much text | Image contains too much text (legacy rule) | Reduce text overlay on your image — Meta recommends less than 20% text |
Video processing failed | Meta couldn't process your video file | Re-upload the video. Ensure it's a valid MP4 file. Try reducing resolution or file size |
Budget and Billing Errors
ErrorCauseFix | ||
Ad account disabled | The ad account has been disabled by Meta | Check your ad account status in Meta Business Manager. May require an appeal |
Billing threshold reached | Account has unpaid charges | Update payment method in Meta Business Manager |
Budget too low for objective | Meta requires a higher minimum budget for certain objectives/audiences | Increase your daily budget |
Targeting Errors
ErrorCauseFix | ||
Audience too narrow | Your targeting combination results in an audience too small to deliver | Broaden your targeting: add more countries, widen age range, or remove audience restrictions |
Invalid custom audience | The selected custom audience no longer exists or is expired | Remove the audience or select a different one |
Rate Limiting
ErrorCauseFix | ||
Too many API calls | Meta's rate limit reached | Wait a few minutes and try again. For bulk launches, reduce batch size |
Too many objects | Trying to create too many elements in one call | Reduce the number of ad sets or ads per campaign |
Understanding the Progress Tracker
During publish, the progress tracker shows each step:
StatusMeaning | |
⏳ In Progress | Currently being processed |
✅ Completed | Successfully created on Meta |
❌ Failed | Error occurred — hover/click for details |
🔄 Rolling Back | Cleaning up after a failure |
If a campaign shows ❌, click on it to see the detailed error message including:
Which step failed (campaign creation, ad set creation, media upload, or ad creation)
The specific error message from Meta
Account and creative details for reference
Stale Run Detection
If a campaign publish takes more than 5 minutes without progress, Wevion automatically marks it as failed. This can happen due to:
Network issues between Wevion and Meta
Meta API outages
Very large video files timing out
In this case, check your Meta Ads Manager to see if any resources were partially created, and retry the launch.
Step-by-Step: Resolving a Failed Launch
Read the error — Check the progress tracker for the specific error message
Identify the layer — Is it a validation error (grid), backend error, or Meta API error?
Fix the issue — Use the tables above to find the fix
Retry — After fixing, click Publish again. Wevion already cleaned up any partial resources, so you're starting fresh
Frequently Asked Questions
Q: My campaign was "rolling back" — what does that mean? A: When a failure occurs after partial creation (e.g., campaign created but ad set failed), Wevion automatically deletes the partially created resources on Meta. This prevents orphaned campaigns cluttering your ad account.
Q: I fixed the error but the publish fails again with the same message. A: Make sure you're addressing the root cause. If it's a Meta-side issue (account disabled, billing), fix it in Meta Business Manager first. If the error mentions rate limiting, wait a few minutes before retrying.
Q: Can I see a history of failed launches? A: Yes. Wevion stores all worker run results including failures. You'll see in-app notifications for each failed launch with the error details.
Q: The error message is unclear — who should I contact? A: If the error comes from Meta (usually starts with a numeric code), check Meta's Business Help Center. If the error seems to be from Wevion, contact our support team with the error message and your campaign configuration.
Q: Why did my video upload fail? A: Video uploads to Meta can fail for several reasons: file too large, unsupported codec, or Meta processing issues. Try re-encoding the video as H.264 MP4 at a lower resolution. Video processing on Meta's side can take up to 10 minutes for large files.