Why did my launch fail and how do I fix it?

A launch rarely fails as a single all-or-nothing event. uplads creates each ad independently, so when you reach the final step you may see some ads go live while others fail. This article explains how to read those results, which errors fix themselves, which need your attention, and where to find the full story.

Reading per-creative failure reasons in the results

On the Launch step, each creative gets its own row with a status dot and a short label:

• Green dot — "live": the ad was created successfully.
• Amber dot — "partly live": the ad succeeded in some ad sets but failed in others.
• Red dot — "failed": the ad could not be created in any ad set.

When the launch finishes you'll see either "All ads launched successfully!" or "Launch completed with errors" along with a "X succeeded, Y failed" summary.

For a relaunch of existing ads (see How to relaunch existing Facebook ads), uplads shows a "Why these failed" box right on this screen, listing each ad name with Meta's exact error message — for example, "Dynamic creative without product set id." For a standard bulk launch, the one-line summary lives here and the full per-ad reason is on the Launch Details page (covered below).

Transient errors that auto-retry

Some failures are temporary — Meta is briefly rate-limited or a service is momentarily unavailable. uplads recognizes these and retries automatically, so you usually never see them. Behind the scenes the worker retries each transient batch up to 3 times with a short, increasing backoff.

Errors treated as transient (and retried) include:

• Rate limits — app, user, or Page-level throttling (Meta error codes 4, 17, and 32).
• Temporary unavailability — "service temporarily unavailable" and Meta's generic "unknown error" (codes 1 and 2).
• Anything Meta itself flags as retryable — when Meta's response sets is_transient.
• A known transient hiccup when several ads hit the same ad set at once (subcode 1487390), which clears on a retry.

Video uploads have extra patience built in: if Meta is still processing a video, uplads waits and polls rather than failing. You'll see "Meta is processing the video… (can take a few minutes)" during this time. If processing genuinely stalls, the launch fails with a message telling you to re-run it — and the already-uploaded video is reused, so the retry is fast.

Permanent errors that need a fix

If an error survives the automatic retries, it's a real problem that needs your input. Common permanent causes:

• Rejected or non-compliant creative — the image/video or copy violates Meta's policies.
• An invalid field — a malformed destination URL, a missing Page, or a call-to-action that doesn't fit the objective.
• Structural mismatches — for example, "Meta allows only one ad in an ad set with dynamic creative," or a dynamic creative missing a required product set.
• Unsupported file type — only image and video creatives are supported for Meta.
• Expired authorization — if your Meta token can't be used, see How to reauthorize or disconnect your Meta account.

Fix the underlying issue (swap the creative, correct the URL, reconnect Meta, or adjust the ad set), then use Retry failed to recreate only the ads that didn't succeed. Retrying leaves the ads that already went live untouched. For Meta-specific error wording, see Ad set limits and common Meta errors explained.

Relaunch fallback notices

When you relaunch an existing ad using Copy with Post ID (to keep likes, comments, and shares pooling on the same post), Meta sometimes refuses to rebuild a fresh post-ID creative for Advantage+ Creative or catalog ads. Rather than fail, uplads reuses the source ad's creative directly and shows an amber "Post ID applied via shared creative" notice.

This is not an error — the relaunched ad still points at the exact same post, so engagement carries over as intended. The only difference is cosmetic: in Meta Ads Manager's edit view you'll see the creative editor instead of "Use Existing Post." The notice exists so this doesn't surprise you later.

Where to find full detail

For the complete reason behind any failed ad:

1. Click View launch details on the results screen (or open the launch from the Launches list).
2. Each item shows its status and the stored error message from Meta.
3. From here you can Retry failed (only failed items) or Retry all (everything that isn't already live).

Workspace-level events — including launches and retries — are also recorded in the audit log. See How to view the audit log of workspace changes and How to track launch progress and read results.

Still stuck? If ads seem to launch but don't appear in Meta, read Why don't my launched ads appear in Meta Ads Manager?.