## **🔍 What Is Happening?**

If Content Genius is returning the same score for two or more different articles, this is caused by a temporary outage or degraded performance from the underlying AI provider that powers the content scoring engine. When the AI provider cannot process new requests, scoring may get stuck at the same value rather than calculating a fresh result for each article.

This is a platform-side issue, not a problem with your content or account settings. No data is lost, and scoring will return to normal once the AI provider recovers.

## **⚠️ How to Confirm This Is the Cause**

- Two or more articles receive the exact same numerical score despite having clearly different content.
- The score does not change after editing the article and re-running the scorer.
- The issue affects multiple projects or articles around the same time.

## **🚀 What to Do**

Because this issue is caused by an AI provider outage on the platform side, there is no self-serve fix that will force scoring to recover. The recommended approach is to wait and retry:

1. **Wait and retry.** AI provider outages are typically short-lived. After some time has passed, return to the affected article in Content Genius and attempt to score it again.
2. **Try a different article.** Open a second article and score it. If it returns a different, plausible score, the service has recovered and you can re-score the original article.
3. **Check again later.** If the issue persists, the provider may be experiencing a longer incident. No action on your end is required for the fix to take effect — scoring will recover automatically once the provider is back online.

## **💡 What You Should Know**

- **Your content is safe.** A stuck score does not affect your saved drafts, article history, or any published content.
- **Scores are recalculated fresh each time.** Once the AI provider is back online, every new scoring request will produce an accurate, individualised result for your article.
- **This is not a billing or account issue.** The problem is entirely tied to AI provider availability and resolves automatically.
- **Avoid making major edits based on a stuck score.** If you suspect scoring is affected, wait for the service to recover before using the score to guide optimisation decisions.

## **🛠️ Still Seeing the Same Score?**

If the score remains identical across multiple articles after waiting, please reach out to our team. To help us investigate quickly, have the following ready: the name of the affected project, the article(s) showing the stuck score, and the approximate time you first noticed the issue.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.