## 🔍 What This Issue Looks Like

You fill in the Blog Headline and Blog Summary fields for your press release, the dashboard shows both fields as complete, but when you attempt to publish, the distribution is blocked. The underlying API reads those fields as **null**, and you receive an error similar to: *"The blog headline field is required."* Your press release stays unpublished and your HDC quota is not consumed.



## 📋 What Caused This

This was a confirmed platform bug where the PR Distribution system did not correctly pass filled-in blog metadata to the publishing API, causing it to treat populated fields as empty. An engineering fix has been deployed to production, so new press releases should publish without this error. Failed press releases also do not consume your HDC quota, so you will not lose credits for a blocked attempt.



## ✅ Steps to Resolve

1. Navigate to the PR Distribution section of the platform.
2. Locate the press release that failed to publish. If it shows a failed or blocked status, do not attempt to re-submit it immediately — first confirm the steps below.
3. Open the press release and verify that the Blog Headline and Blog Summary fields contain your intended content. Even if they appeared filled before, clear each field and re-enter the content to ensure the platform registers the values correctly after the fix.
4. Save your changes before attempting to publish again.
5. Proceed to publish the press release. With the engineering fix now live in production, the API should correctly receive the blog metadata and allow distribution to proceed.
6. If the press release still shows a blocked or failed status after re-entering your content and saving, do not re-submit multiple times. Contact support using the method described below so a specialist can review your specific press release.

## 💡 About Your HDC Quota

Press releases that fail due to this error **do not consume your HDC quota**. A failed distribution is not counted against your credits. If you believe credits were incorrectly deducted as a result of this bug, note the affected press release details and contact support — the team can review and apply a correction where appropriate.



## ⚠️ If the Problem Persists

This bug has been patched, but if you continue to see the same error after following the steps above, it is important to escalate promptly rather than retrying repeatedly. Provide support with the name of your press release and the approximate time you attempted to publish so the team can investigate your account directly.



## 💬 Get Help

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.