Changes to our audit, what they affect, and whether a scenario is worth repeating.
We fixed how the audit handles browser tabs and provider responses. A response error produces a technical failure, without a score for that agent.
Offline tests passed. The live release and its effect on earlier audits are not confirmed, so we cannot yet recommend repeating a scenario.
We updated how the audit handles scrolling, unsupported actions and response limits. An unsupported action produces a technical failure, without a score for that agent.
We have tested the changes offline. A live release and its effect on earlier audits are not confirmed, so we cannot yet recommend repeating a scenario.
We tightened how we match model names to our internal cost table. This does not change customer prices or how we score a website.
A change to cost accounting alone does not require a new audit.
We fixed how report generation opens local files on Windows. The change affects report preparation, not the agent’s findings about a website.
This report preparation fix does not require repeating the scenario. It does not change a completed audit’s score.
If an older report has no version details, we cannot reliably match it to a change. These updates do not start an audit, use your balance or send you an email.