🔍 Overview
Some users have reported that after updating the niche field inside default_ai_settings through the API, the new value does not persist. Instead, the field returns null when queried. This is a known platform bug that has been identified, escalated, and resolved by the Search Atlas engineering team.
⚙️ What Causes This Issue
This problem was caused by a bug in Atlas Brain that prevented the niche field from being written and retained correctly when updated via the API. The field would appear to accept the new value, but it would not save, and subsequent reads would return null. This affected Brand Vault niche field updates made through the API integration.
✅ Current Status
The engineering team has confirmed that this bug has been fully resolved. The fix was prioritized, developed, reviewed, and released. If you experienced this issue before the fix was deployed, your niche field may still show null and will need to be set again.
🚀 Steps to Resolve
- Retry your API update. Now that the underlying bug is fixed, attempt to update the niche field via the API again using the same request you used previously.
- Verify the value persisted. After submitting the update, retrieve the record via a follow-up API read request to confirm the niche field now returns your intended value rather than null.
- Re-enter the value manually if needed. If the field still shows null after retrying the API update, try setting the niche field directly within the platform as a temporary measure while you confirm the API call is formatted correctly.
- Check your API request format. Ensure the niche value is being passed correctly within the default_ai_settings object in your request payload. A malformed or missing field key can cause the value to be silently dropped.
💡 Tips to Prevent This Going Forward
- After any API update to settings fields, always perform a follow-up read request to confirm the value was saved as expected.
- If a field returns null unexpectedly after an update, treat this as a signal to retry the request or contact support — it may indicate a transient issue rather than an error in your code.
- Keep your API integration up to date, as platform fixes may occasionally require that previously failed operations be retried.
📞 Still Seeing the Issue?
If the niche field continues to return null after following the steps above, this may indicate a different underlying problem specific to your account or project. If you need further assistance, reach out to our support team and a member of our team will be happy to help.