# Troubleshooting > Fixes for the common problems: drafts that don't arrive or get stopped, deliveries that fail, pages that 404, autopilot that won't unlock, missing Search Console data, custom domains and Pilot. Start with what the dashboard already tells you: the **Needs attention** tab in the review queue (drafts that couldn't be written, with the reason), **Needs attention** on the Publishing page (deliveries that failed, with the error), and the notification bell. Then find the symptom below. ## Drafts :::details No new drafts are arriving - **Give it a few minutes.** A new source is checked straight away, but research and writing take a minute or more per article. - **Check this month's articles** on Plan & usage. At the limit, new drafts wait for the reset. See [Plans and usage](/docs/plans-and-usage). - **Check your sources** under Sources: a source marked **Failing** can't be read. If you have no sources and no keyword targets, there's nothing to write from. - **Check the activity feed on Overview.** Writing pauses itself when a dozen drafts have waited ten days, when writes keep failing, or when deliveries keep failing, and the feed says which. Review some drafts or fix the destination and it resumes. ::: :::details A draft says "Not for your customers" or "about a real person" Seovyn stopped it before writing, because the topic didn't fit the audience in your brand voice, or because it would be about a named person. If you want it anyway, choose **Retry**: it's written regardless. If good topics are being stopped, make the **Audience** and **Product one-liner** in [brand voice](/docs/brand-voice) more accurate. See [How topics are chosen](/docs/choosing-topics). ::: :::details A draft failed to write Choose **Retry** under Needs attention. A failed draft gave its article back, so a retry uses one again. If several fail in a row, Seovyn pauses new writing for 12 hours and tries again on its own. ::: :::details Articles feel generic or off-brand Tune [brand voice](/docs/brand-voice), especially the audience. Add [site knowledge](/docs/site-knowledge) notes and answer the **Questions only you can answer**: first-hand detail is what makes an article yours. Reject weak drafts with a reason instead of fixing them quietly, so the same problem doesn't come back. ::: ## Publishing :::details A delivery failed The error is under **Needs attention** on Publishing. Fix the setting, and the next delivery uses it. | Destination | Check | |---|---| | **WordPress** | The site address, username and application password (Users → Profile → Application passwords). The REST API must be reachable | | **Shopify** | The app has the `read_content` and `write_content` scopes and is installed on the store | | **Webflow** | The token has CMS read and write, Sites read and Assets write access | | **Wix** | The API key has Blog, Rich Content and Media Manager permissions, and the site ID is right | | **Notion** | The integration has been added under ••• → Connections on the blog database | | **Ghost** | The Admin API key (not the Content API key) from a custom integration | | **Webhook** | Your endpoint answers `2xx` within 8 seconds and verifies the raw body. See [Webhook reference](/docs/webhook-reference) | Failures that can pass on their own, like your site being down, are retried six times over about a day. ::: :::details The article was delivered but the page 404s **GitHub or Next.js.** Markdown files in a repo don't become pages by themselves: something has to render them. For Next.js App Router sites, Seovyn generates and merges the render routes for you; check the card under **Render your content** on Publishing. If that pull request couldn't merge (usually a branch protection rule), merge it yourself. On another framework, check the **Content path** on Publishing: Seovyn sets it to the folder your existing posts live in, and a site with no posts yet needs something that renders that path. Or switch to the [webhook](/docs/webhook-reference). See [GitHub and Next.js](/docs/github-and-nextjs). **Slow builds.** A static site needs time to build after a merge. Seovyn checks the page over the next day and a half before marking it **Not found**. ::: :::details Approved articles aren't going anywhere If no destination is connected, approved articles wait (the notification bell says so). Connect one on Publishing and they go out. If publish pacing is on, they go out in turn: the publishing queue on Overview shows when the next one will. ::: ## Autopilot :::details Autopilot hasn't unlocked after five approvals All three must hold: five approvals in a row with no rejection between them, **none of them edited** (editing clears a draft's score), and each of the five scored **70 or more**. An edited or low-scoring approval holds autopilot off until it's no longer among your last five. See [Autopilot](/docs/autopilot). ::: :::details Autopilot didn't publish a draft On autopilot, a draft that won't approve itself says why in the queue, for example a score below 75, a landing page, a topic fit below 70, or a random spot check. It's waiting for you. See [what autopilot publishes](/docs/autopilot#what-autopilot-publishes). ::: :::details I was moved back to supervised Either you rejected a draft while on autopilot, or recent articles averaged below 65. The activity feed says which. Approve five clean drafts to earn it back. ::: ## Search Console and Google :::details Search Console shows no data New articles need time before Google has anything to report, and Google's numbers run about two days behind. Check that the connected property contains the site you publish to: a `www` property shows nothing for the bare domain. A domain property covers both. See [Search Console](/docs/search-console). ::: :::details An article isn't in Google Most new pages appear within two weeks. If one hasn't, open Search Console's **URL inspection** for its address and request indexing. First make sure the page loads: an article marked **Not found** in the Library never went live. See [Results](/docs/results). ::: ## Hosted site :::details My custom domain isn't live yet Check the DNS record exactly matches what the dashboard shows, with only the short name (such as `www`) in the name field. On Cloudflare, set it to **DNS only**, not proxied. DNS can take a while to spread; Seovyn keeps checking and switches over as soon as it's ready, and **Check now** checks immediately. See [Seovyn-hosted site](/docs/hosted-site#use-your-own-domain). ::: ## Browser Agent :::details Pilot shows as offline or not connected Open Pilot's side panel and choose **Sign in with Seovyn** again, making sure you approve it for the right organization (choose **Switch** if not). The Browser Agent page shows the runtime as online once it's connected. See [Browser Agent](/docs/browser-agent). ::: :::details A Pilot task stopped It's probably waiting for your approval (see **Needs attention** on the Browser Agent page; requests expire after five minutes), or this month's Browser Agent budget is used up, in which case it resumes after the reset. ::: ## Still stuck? Use the chat in the corner of this page, or write to support@seovyn.com with your account email, the organization, and what you saw.