| urgent | The finding has been classified as a high priority. | Check the evidence and the source date before acting. |
| New / Updated | New: the finding appeared since the last check. Updated: an existing finding changed. | An Updated card can carry a different figure from yesterday. Read the current one. |
| Show 2 more | Overview keeps four cards in place and folds the rest under this control. | Open it before concluding there are only four findings. The heading count includes them. |
| Shown anyway | Your standing note would have hidden this card, but a serious finding pierces the note. | Read it. The pill is there so the override is never silent. |
| 2 findings | The card covers more than the one item in its headline. | View products expands the card and lists each item with its own figure. They should add up to the headline; the headline names one example, not the whole set. |
| nothing to report | That check ran and its query came back empty. | Read it as that check, on the data it read. It is not a statement about the whole business. |
| looked at 1, none big enough | That check found rows and judged them too small by its own bar. This is the check's threshold, not your sensitivity setting. | Nothing to change under Edit. Ask Winston about the item if you want to see it anyway. |
| 3 findings | On a Details row: how many findings that check has on your page right now. | Findings are counted, not cards. A grouped card can hold all three. |
| checked 11:53 PM | On a Details row: when that check last ran. | Compare it with the card's POS data as of line; they answer different questions. |
| Biggest held back: … | The largest finding a check withheld, in that check's own units. | A way to judge whether the sensitivity setting is costing you something you care about. |
| didn't finish, retrying 3:40 PM | The check failed and Winston will try again at the time shown. | Wait for the retry. If it keeps failing, contact Support with the check name and time. |
| couldn't sign in to Snowflake / Snowflake not connected / no store data yet / data only through Sep 28 | Why a check could not run: the warehouse refused the login, is not connected, has no rows yet, or is behind. | An admin should look at Settings → Connections and Data Warehouse. These are gaps, not results. |
| 7 checks ran · 1 not applicable | The coverage line under Watching. Only couldn't run is shown in amber, because only that is a gap in what Winston knows. | No checks could run means nothing on the page is an all-clear. |
| 12 below your sensitivity | That check found things, and your sensitivity setting is holding them back. | Change sensitivity under Edit if you want the smaller ones. See Monitoring settings. |
| runs after a holiday | The check only applies in a particular situation, which is not in play. | Nothing to do. Its silence is not a result. |
| Nothing from Sales and margin right now | The area is being watched and has nothing on your page at the moment. | Open Details for the individual checks behind the area. |
| 2 findings resolved today | Findings no longer reported. Each line names the check: "no longer reported by the Stockout risk check". | Open it and read which check stopped reporting and when. A cleared finding is not proof that anything was done about it. |
| Winston hasn't checked your stores yet | Connected, but no check has read your data successfully. | Open Details for each check's reason. Not an all-clear. |
| Winston can't sign in to your store data | Every check stopped for the same reason, and the page names it. | Reconnect the warehouse or use the Contact support button, which comes with the description filled in. |
| All stores look normal right now | A check read your data and found nothing it would raise. | Still read the coverage line: it says how many checks that claim rests on. |
| Overview requires a connected Snowflake connector | The blurred preview, shown to any workspace without a connected data warehouse. | The sample cards are not your data. Connect POS, then come back. |