When you publish a campaign, AdStellar sends it to Meta’s API. Sometimes errors occur — here’s how to understand and fix them.
How Publishing Works
Campaign publishing runs as a background job. You can track the status of any publish on the Campaigns > Launches tab.
Each launch moves through these statuses:
Partial Publish
Some ads may succeed while others fail. The launch card shows which ads published and which had errors. Successfully published ads are already live (paused) in Meta — you don’t need to republish the entire campaign.
Expand the launch card to see per-ad status. You only need to fix and retry the failed ads.
Auto-Retry
AdStellar automatically retries transient errors — like Meta rate limits and temporary server errors — up to 3 times. You don’t need to take action for these. Just wait and check the launch status again.
Common Errors
If your campaign appears in Meta Ads Manager but shows 0 ad sets or 0 ads, this usually means the publish job is still processing. Check the Launches tab in AdStellar — if the status is “Processing,” wait for it to complete. If the status is “Failed” or “Partial,” expand the launch card to see error details. Large campaigns with many variations can take several minutes to fully publish.
Campaigns Publish as Inactive
By design, AdStellar publishes all campaigns, ad sets, and ads in a PAUSED state. This is intentional — it gives you a chance to review everything in Meta Ads Manager before spending money. To activate your ads, follow the Turn On Campaign guide. You’ll need to turn on both ad sets AND ads for delivery to begin.
If you don’t turn on your ads in Meta Ads Manager, they will never start delivering — even though they published successfully from AdStellar.
Fail-Fast vs Retryable Errors
Not all errors are retried. AdStellar categorizes errors into two groups:
Retryable (transient)
These are automatically retried up to 3 times with increasing delays:
- Rate limits — Meta API codes 4, 17, 613
- Transient server errors — Meta API code 2
Fail-fast (permanent)
These errors won’t be retried because they require manual action:
- Invalid token — Code 190. Resync your Meta connection.
- Account disabled — Code 1487553. Contact Meta support.
- Policy violations — Code 1487890. Update your creative to comply with Meta’s ad policies.
- Spending limit reached — Code 1487696. Increase your spending limit in Meta Business Manager.
AI Builder Errors
When AI campaign generation fails, you’ll see an error with an ID like AI-XXXXXX. Include this ID when contacting support.
Common AI errors:
- Timeout — Generation took too long. Try again with fewer variations or a simpler brief.
- Rate limit — Too many concurrent AI builds. Wait a minute and retry.
- Validation — The generated campaign didn’t pass AdStellar’s checks. Review the error details and adjust your inputs.
Always include the AI-XXXXXX error ID when reporting AI issues to support — it helps us diagnose the problem faster.
Still Stuck?
- In-app chat — Click the support icon inside AdStellar.
- Email — Contact support@adstellar.ai with your error details and a screenshot of the launch card.
