🔍 What Is This Issue?
When editing a blog entry in Search Atlas, you may encounter a 400 error accompanied by a spinning star icon that continues indefinitely without loading the page. This prevents you from accessing or saving your blog content.
This article explains what this error means and what to do if you experience it.
⚙️ Why Does This Happen?
A 400 error in the Blog Builder indicates that the platform was unable to process a request. Based on known occurrences, this issue has been caused by a platform-side problem affecting blog entry loading — not a setting or configuration on your end. Customers experiencing this error at the same time are typically impacted by the same underlying backend issue.
🚀 What You Should Do
Because this is an outage-type issue resolved on the backend, there are no customer-side steps that will reliably fix it. If you encounter this error, please do the following:
- Note the exact error message — record any error code or text displayed on screen (e.g., "400 Bad Request").
- Note the timestamp — record the date and time (including your timezone) when you first encountered the issue.
- Note the affected blog entry — record the name or URL of the blog entry you were trying to edit.
- Contact our support team — share the above details so our team can investigate and apply a fix on the backend.
✅ What to Expect
Once our engineering team identifies and resolves the underlying platform issue, the Blog Builder will load your entry normally and the spinning star icon will no longer appear. No changes to your blog content or account settings are required on your part.
🛡️ If the Issue Recurs
If you see this error again in the future, follow the same steps above and contact support right away with your project name, the exact error message, and the timestamp. Early reports help our team detect and resolve platform issues faster.
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.