Use this article to diagnose and fix the most common Signal Genesys distribution failures — press releases stuck in Pending, AI summaries rejected for length, and API token errors when publishing a press release.

Signal Genesys distribution depends on backend validation, outlet syndication queues, entity verification, external publisher acceptance, Google indexing, and API synchronization between Search Atlas and Signal Genesys. Because distribution spans multiple third-party systems and publishing partners, some delays and partial propagation are expected.

## ⚠️ Error 1: Press Release Stuck in "Pending" and Not Distributing

This is the highest-volume Signal Genesys issue (41,000+ occurrences). The distribution service rejects a press release when required fields fail backend validation. Common causes include missing fields, invalid formatting, summaries exceeding limits, invalid scheduling dates, incomplete contact information, or malformed company profiles.

**How to fix it:**

1. In the Search Atlas left sidebar, go to **Authority** → **PR Distribution** (Press Releases) → [Your PR] → **Edit**.
2. Confirm all required fields are completed: headline, body, summary, company name, contact details, and website URL.
3. Ensure the body contains at least **300 words**.
4. Confirm the summary is under **45 words**.
5. Verify the scheduled distribution date is not in the past.
6. Remove unusual formatting or unsupported symbols.
7. Save the press release again before resubmitting.
8. Retry distribution after refreshing the dashboard.
9. Test with a simplified version of the press release if validation keeps failing.
10. Contact support if the press release stays stuck longer than **2 hours**.

Validation failures happen before distribution begins, so saving and resubmitting often refreshes invalid backend states automatically. When all required fields are complete and valid, distribution proceeds normally.

### Visual status glitch on "publishing"

If your press release appears stuck on "publishing" or "publishing content" for more than a few hours, it may have failed validation even though the UI did not update. Refresh the dashboard or open the PR details. If the status has not changed after 24 hours, contact support for backend verification.

## ⚠️ Error 2: AI Summary Rejected — "Must Contain at Most 45 Words"

Signal Genesys enforces a strict 45-word limit for press release summaries. AI-generated summaries occasionally exceed this limit even when they look short on screen.

**How to fix it:**

1. Open **Edit Press Release** → **Summary**.
2. Count the words manually.
3. Reduce the summary to **45 words or fewer**.
4. Write one concise sentence that covers what happened, who is involved, and why it matters.
5. Remove filler language and marketing phrases.
6. Use the company name only once.
7. Save the summary before resubmitting.
8. Re-run AI summary generation if it is available.
9. Contact support if valid summaries keep failing validation.

Word count validation is strict and automated, and hyphenated words may count differently depending on formatting. Once the summary is within the 45-word limit, the press release proceeds to distribution.

## 🔑 Error 3: "Invalid Scope Provided — Check API Key Permissions"

This error indicates a platform-level API permission mismatch between Search Atlas and Signal Genesys. It is not caused by your account settings.

**How to fix it:**

1. Refresh the Signal Genesys dashboard and retry distribution.
2. Confirm you are signed in to the correct Search Atlas account.
3. Complete the steps in the next section to remove and re-check your Signal Genesys API token.
4. Contact support if the error persists after re-checking your token.

Once the correct API token is in place and permissions match, distribution resumes normally.

## 🔑 Signal Genesys API Error When Publishing a PR — Remove and Re-Check Your API Token

If you get a Signal Genesys API error while publishing a PR article (including categories such as pop culture), the most common cause is an incorrect or stale API token. Removing the token and re-running the PR with the correct token resolves it in most cases.

**How to fix it:**

1. Open your Signal Genesys integration settings where your API token is stored.
2. Remove the existing API token.
3. Confirm you have the correct Signal Genesys token — using a token from another service or account triggers this error.
4. Re-enter the correct token and save.
5. Run your PR again.
6. Contact support if the API error continues after re-checking the token.

Our engineering team is actively investigating the root cause of this API error under ticket **SPE-868**. If removing and re-adding the correct token does not resolve it, reach out to support and reference SPE-868 so we can link your case to the investigation.

## ⚠️ "Please Fill Knowledge Graph's Website in Order to Deploy"

If you receive "Please fill knowledge graph's Website in order to deploy" even though you already completed the Knowledge Graph website field:

1. Re-save the Knowledge Graph entry.
2. Wait 2–3 minutes for synchronization.
3. Create a new press release draft.

If the error persists, contact support.

## ✅ Known Issue (Resolved): Duplicate Headline Detection

If the system rejects your press release as a duplicate headline even after you change the headline, this was caused by a validation cache bug (ticket AB-1059). Confirm you are running the latest version of Signal Genesys; if the issue persists, contact support.

**🎯 You now know how to clear a Pending press release, fix a rejected 45-word summary, and resolve Signal Genesys API token errors by removing and re-checking your token. If your PR still fails to publish after these steps, contact Search Atlas support and reference SPE-868 for the latest status.**