# My launch was refused or ads failed Why Launch stays greyed out, why Meta refused a launch, and what to do with ads that failed, were stopped, or were sent without a confirmation. ![The Launcher’s Structure step: one campaign, one ad set and two ads, each marked Needs ad copy, above the Launch button](https://docs.omnymous.com/media/getting-started/launch-your-first-campaign/structure.09fd4aec.avif) A launch fails in one of two places: before it starts, when **Launch** stays greyed out, or on Meta, when the last step reports what it could not create. Start from what the Launcher says. ## Launch is greyed out The line beside **Launch** (above it on a phone) says what is still missing, as in **Needs ad account · page +3**. Rest the pointer on **Launch** for the whole list, or press the line to open the first fix. The most common: | What it says | What to do | | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | Give every ad a headline and a primary text | Open each ad marked **Needs ad copy** and write its copy. | | No compatible creative–page pairs yet | No page tells the same story as your creatives. Choose other pages, or review why each pair was left out. | | Choose a Meta ad account, or Choose a Facebook Page | Press **Settings** and choose them under **Account**. | | Connect Meta | The store has no Meta connection. Connect it: see [Manage your ad platforms](https://docs.omnymous.com/workspace/integrations#connect-a-platform). | | Reconnect Meta: it stopped authorizing this store | Reconnect it, below. | | Give the connected Meta login an ad account | The login Meta was connected with reaches no ad account. Give it access in Meta Business Settings, then check again. | | Launch in progress | Another launch from this store is still running. Wait for it to end. | ## Meta stopped authorizing the store Launches go into the ad account and Page of a connected Meta business. When Meta stops authorizing Omnymous, for example after the password of the connected login changes, **Launch settings** reads **Reconnect needed** beside **Meta account**, and **Integrations** says the same on Meta’s row: ![Meta’s row in Integrations: Reconnect needed, stopped updating 2 days ago, with Reconnect, and the notice that Meta stopped authorizing this connection](https://docs.omnymous.com/media/workspace/integrations/lapsed.c8153b31.avif) Press **Reconnect** on that row, sign in on Meta with the login that runs your ads, and approve Omnymous. Then launch again: see [Reconnect a platform](https://docs.omnymous.com/workspace/integrations#reconnect-a-platform). Campaigns already running on Meta keep running meanwhile. ## The launch was refused **Launch refused — nothing was created** means Meta or Omnymous turned the launch down before a single ad was made. The reasons are listed under it: fix what is listed, then launch again. A daily budget above the store’s **Budget guardrail**, under **Account** in **Launch settings**, is refused the same way: lower the budget, or raise the guardrail if the budget is right. **Launch failed**, with how many ads failed, as in **All 2 ads failed**, means Meta refused every ad: each one says why. See [Retry failed ads](https://docs.omnymous.com/generation/launcher/launch-and-recover#retry-failed-ads). ## Some ads failed **2 of 4 ads created**, with your numbers, means Meta refused the others, each with its reason. Fix what the reasons say, then press **Retry 2 failed ads** (with your number). Only the failed ads are sent again: the ads already on Meta are not sent twice. ## Retry says Not yet An ad that was sent to Meta without a confirmation may exist in Ads Manager even though Omnymous never heard back. Before retrying it, Omnymous checks Ads Manager for it, so that no ad is paid for twice. Until that check is done, **Retry** answers **Not yet**, with the time you can retry. Retry then. ## You stopped a launch **Stop launch** ends it after the ad set in progress: **Launch stopped**, with how many ads were created. Ads created before the stop stay on Meta. Pause or delete them in Ads Manager if you do not want them. ## The ads were created paused **Created paused — enable delivery in Ads Manager** means the launch ran with **Initial status** set to **Paused**: the campaign is on Meta, waiting for you to start it there. To start the next launches at once, choose **Active** in **Launch settings**. ## Still stuck Write to with: - your store’s name and the campaign’s name; - the exact words on the last step, with each failed ad’s reason; - when you launched, with your time zone. ## Related - [Launch and recover](https://docs.omnymous.com/generation/launcher/launch-and-recover): Press Launch, watch Meta create each ad, and know what to do when a launch is stopped, refused, or leaves ads failed or unconfirmed. - [Launch your first campaign](https://docs.omnymous.com/getting-started/launch-your-first-campaign): Pick creatives and the page they lead to, let the Launcher plan the Meta campaign, set its account and budget, and launch it. - [Manage your ad platforms](https://docs.omnymous.com/workspace/integrations): Connect Meta, Google or TikTok to a store after setup, reconnect one that stopped updating, refresh what it reads, and disconnect it. --- Source: https://docs.omnymous.com/troubleshooting/launch-problems