How to report a bug to Nomic Support
A great bug report is the difference between a same-day fix and a back-and-forth that lasts a week. Use this checklist and we can usually reproduce the issue without another round-trip.
Always include
- The URL — exact page you were on when it broke. URLs encode the project, workflow, and run, so this often tells us 80% of what we need.
- What you expected vs what happened — one sentence each.
- The exact time and timezone of the failure (down to the minute is enough).
- Browser + OS — "Chrome 142 on macOS 26.3" is perfect.
- The path you took — which buttons / links you clicked, in order, to trigger the issue.
Strongly recommended
- Screenshot. Capture the entire window, not just the error region — the navbar and URL bar carry useful context.
- Short screen recording. A 10-20 second clip of the broken behavior beats a long written description for anything that's "the page froze" or "the spinner just spins." macOS: Cmd+Shift+5. Windows: Win+Shift+R.
- Console errors. Open the browser dev tools (Cmd+Opt+I / Ctrl+Shift+I), click the Console tab, screenshot anything in red.
- Network errors. In dev tools → Network, screenshot any red rows around the time the bug happened.
Helpful when relevant
- File or workflow names — easier for us to look up than IDs.
- Job / run / task ID if the page shows one in the URL or in a corner.
- A second tab / second user — does the issue reproduce for a teammate, or only for you?
Where to send it
- Nomic Support — email or in-app support widget. Use this for anything customer-impacting or anything urgent.
- Your account team — if your team has a dedicated Slack channel with Nomic, that's the fastest path. Drop the bug there with the same checklist above.
Speed tip
If you're stuck and need to keep working, screenshot first, then reload. Reloading often clears the issue but also destroys the evidence we need to fix it permanently. A quick screenshot + URL takes 10 seconds and saves us all another conversation.