The Connection Status Report lists every tribe and the state of its sales integration. When figures look wrong, this is the first place to look — a silently broken connection is far more common than a broken report.
The columns
| Column | Tells you |
|---|---|
| Last sync | When Gorilla Dash last talked to the system. |
| Last transaction | When it last received anything. |
| Last sale | When the most recent sale arrived. |
| Last quote | When the most recent estimate arrived. |
The statuses
- Last sync successful — working.
- Last sync failed — open it and read the error log.
- Sync in progress — running now.
- Last sync timed out — usually the point of sale being slow or unreachable.
- No integration configured — nothing has been set up for this tribe.
- Never synced — configured but has never successfully run.
- No connection — no connection record at all.
Investigating one
Open a tribe for its connection status, its Error log and its credentials, where the API details can be revealed and copied. Clear Errors empties the log — do that after fixing something, so the next failure is obvious rather than buried.
Make it a routine
Scan this screen weekly and sort by last sync. A connection that broke a fortnight ago has already put a hole in the reports that everybody will argue about later — and re-syncing usually only reaches back so far, so the sooner it is caught the more of the data comes back.
If a sale is missing but the connection is healthy
Check that the order reached a status you have mapped as a sale. An unmapped status is not a failure — Gorilla Dash simply does not know it means sold.