Two bug fixes have been shipped for OTTO and Site Audit, addressing issues with the Raw JSON Schema editor and a concurrent loader race condition in the OTTO v3 Issues Table.
✨ What's New
This release resolves two bugs that could disrupt your experience when working with schema markup in OTTO:
- JSON Schema editor node highlighting: The Raw JSON Schema editor was incorrectly highlighting the wrong node when removing {} or [] brackets. This has been corrected so the editor now accurately highlights the affected node during edits.
- Concurrent schema generation loader race: A race condition in the OTTO v3 Issues Table caused inconsistent loader behavior when multiple schema generation requests were triggered simultaneously. This has been fixed to ensure the loader state is handled reliably under concurrent operations.
🛠️ How to Use It
- Navigate to OTTO SEO from your Search Atlas dashboard.
- Open the Issues Table to review any schema-related tasks.
- Use the Raw JSON Schema editor to make edits — node highlighting will now reflect the correct element when adding or removing brackets.
- Trigger schema generation as needed, knowing that concurrent requests will no longer cause loader inconsistencies.
🔍 Recognizing These Issues
If you have experienced either of the following symptoms, they are caused by the bugs described above and are now resolved — no action is required on your part:
- Wrong node highlighted in the JSON Schema editor: While editing schema markup in the Raw JSON Schema editor, you may have noticed that deleting a {} or [] bracket caused a different, unrelated node to become highlighted instead of the one you were editing. This was a display bug and did not alter your schema data, but it made it difficult to track which element was being modified.
- Loader spinning inconsistently or getting stuck: If you triggered schema generation for multiple pages or issues at the same time in the OTTO v3 Issues Table, you may have seen the loading indicator behave erratically — for example, continuing to spin after generation completed, or stopping prematurely. This was caused by a race condition when concurrent requests were processed simultaneously.
📋 What to Expect
These are targeted bug fixes with no changes to existing workflows or feature functionality. The JSON Schema editor and OTTO v3 Issues Table should now behave consistently and accurately. No action is required on your end — the fixes are applied automatically.
If you are still seeing incorrect node highlighting or loader inconsistencies after reading this, please hard-refresh your browser (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to ensure you are running the latest version of the platform.
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.