A daily tracking routine you can actually use.
Follow the journey from scheduled question to saved answer and analysis, and understand queue wait, collection time, and jobs that need attention.
Choose your questions and providers.
Keep your active question set focused and choose the providers that matter to your audience. The same question should be asked with the same wording across selected providers.
In Echuno, the Tracking page brings questions, provider outcomes, and daily schedule controls together. Check which questions are enabled before the next collection.
Keep the collection browser connected.
Browser collection depends on an authenticated, connected runner and usable provider sessions. The daily schedule is checked when the runner polls for work; a schedule does not make an offline browser available.
Requests are processed one at a time with a cooldown. Provider sign-in screens, connection loss, maintenance, or a mode that cannot be confirmed can interrupt collection.
Read the states in order.
A queued request is waiting for collection. A running request has been picked up by the browser. A saved answer is available to read, and its structured analysis may still be processing.
- Queued: no answer has been collected yet.
- Asking: the browser is working on this request.
- Saved: the answer has been recorded.
- Analyzing: mention and position extraction is still running.
- Needs attention: inspect the recorded reason before deciding what to do next.
Separate waiting from answering.
Collection time measures the interval from a request starting to its answer being saved. Queue-to-save time includes that interval plus all the time the request waited.
For example, an answer can take 28 seconds to collect and still take seven minutes from queue to save if other questions ran first. Maintenance pauses also increase the total wait without making the AI response slower.
Review exceptions, then patterns.
First inspect incomplete or failed collections. Next, filter saved answers by provider, question, topic, or mention outcome. Finally, compare the actual answers behind a change.
Record follow-up work against the evidence you found. If you revise your website or question set, keep a dated note so later comparisons have context.