If a block on your dashboard looks wrong — fewer rows than expected, a missing segment, or a total that doesn't match what you see in the source — work through this checklist in order. Most cases are caught in the first two steps.
1. 🔌 Is the source caught up?
Open 🔌 Connectors and check the Last synced timestamp for the source the block reads from.
- If it's more than a few hours old (or stuck on a spinner), hit Sync now and re-open the dashboard once the sync completes.
- If the source shows a red error icon, click into it — Zamino will tell you exactly what's broken (refresh token expired, permissions changed at the source, the source's API is down).
2. 🔍 Did the block's filter cut off the data?
Click the ℹ️ icon on the block to see the exact question and filters Zamino used. Two of the most common gotchas:
- A relative date window that's still pinned to the original creation date — "last 30 days" on a block built three months ago still means the same 30 days, not the latest 30. Re-edit the block or use the dashboard's control bar to override.
- A leftover filter from when the block was built — e.g., scoped to a specific entity that's no longer relevant. Edit the block and clear the filter.
3. 🧮 Is the metric still defined the same way?
If your team renamed or redefined a metric recently — say, "revenue" now excludes credit memos — any block built before the change will keep using the old definition until it's edited.
Open the block in the dashboard builder, re-confirm the metric, and save. The next refresh will use the new definition.
4. 🛠️ Did the source's schema change?
Sometimes a source renames a column, deprecates a field, or splits one entity into two. Zamino usually handles this transparently, but occasionally a block breaks because it referenced an exact field that's now gone.
You'll see a yellow warning banner on the block. Click it to:
- See exactly which field is missing.
- Open the question in Chat to rephrase it against the new schema.
- Save the rephrased question back to the block.
5. 🔁 Is a routine running stale?
If the issue is on a routine, not a dashboard:
- Open 🔁 Routines → [your routine] → Notification History.
- Check the last few runs. If they're all reporting "no data" but you know the data exists, the routine's question may be too narrowly scoped or the source it depends on may have disconnected.
Where to go next
- 🔌 Connecting QuickBooks Online — the most common source of "data looks off" tickets.
- 💬 How to phrase a good question — preventing a wonky chart often starts at the question.