🔍 What Is This Issue?
Some users find that schemas generated by OTTO become stuck in a Review status and cannot be deployed. When you attempt to deploy them, the process runs indefinitely and fails — sometimes causing you to lose credits by regenerating the same schemas repeatedly.
This issue has been investigated and fixed by the Search Atlas engineering team. Multiple underlying causes were identified, including a validation error that incorrectly blocked valid schemas from deploying, and a pipeline bug affecting schemas on pages that had no review or rating data. Both have been resolved in platform updates.
⚙️ Why This Happens
- A schema validation bug was incorrectly flagging valid schemas and preventing deployment.
- Product pages with no review or rating data caused certain schema types to get stuck in Review with no fields to correct.
- A broader schema pipeline issue affected AI generation, schema importing, validation, and deployment across multiple domains.
All of these issues have been patched. If you are still experiencing stuck schemas, the steps below will help you resolve them.
🚀 How to Resolve Stuck Schemas
- Refresh the page and check schema status. After the recent platform fixes, some schemas that were previously stuck may now show as deployable. Reload your OTTO session and review the current status of your schemas before taking further action.
- Attempt deployment again. Try deploying the schemas that were previously stuck. In many cases, the engineering fixes applied to the platform will allow previously stuck schemas to deploy successfully without any additional steps on your end.
- Avoid repeated regeneration. If schemas are still showing as stuck, do not keep regenerating them. Each regeneration consumes credits and will not resolve an underlying platform-side issue. Contact support instead so the team can manually deploy the pending schemas and escalate any credit loss on your behalf.
💡 Tips to Avoid Wasting Credits
- Do not regenerate schemas that are stuck — regeneration should be a last resort only after confirming the platform-side issue is resolved.
- If a schema is stuck with no fields to correct and no clear error message, this is a platform-side issue and regenerating will not fix it. Reach out to support instead.
- Keep an eye on your schema quota after any deployment attempts that failed, and report unexplained credit loss to the support team so it can be reviewed and escalated.
📬 Still Experiencing This Issue?
If your schemas remain stuck after following the steps above, please contact the Search Atlas support team via the chat widget in your dashboard. The team can manually deploy pending schemas and investigate any credit loss caused by the issue.