Troubleshooting
The four things that actually go wrong, and what to do about each.
WhatsApp disconnected
Suvi holds its own WhatsApp seat via a paired device. Pairing can drop if the phone that owns the number is offline for a long period, or if the seat is removed from the linked-devices list on that phone.
What you see: the connection indicator in Settings goes red, and Suvi stops replying on WhatsApp while continuing to work everywhere else.
Fix: reconnect from Settings, then Connections. You can scan a QR or use a phone-number pairing code. Message history is not lost and the graph is unaffected.
If it drops repeatedly, the usual cause is the linked device being evicted on the phone. Check that Suvi's session is still listed there.
The brief did not arrive
Briefs run twice daily on a schedule tied to your timezone.
| What else is Suvi doing? | Likely cause |
|---|---|
| Replying normally on WhatsApp | The brief had nothing to report and was suppressed |
| Silent on every channel | The instance or the WhatsApp connection is down |
| Replying, but unaware of recent mail | The mail connection needs reauthorising |
An empty brief is suppressed rather than sent, so a genuinely quiet day produces no message.
A permission was declined
Suvi only claims capabilities it actually has. If a connector is missing a scope, the tools behind it are hidden and Suvi will say it cannot do the thing rather than failing silently.
Fix: reconnect the account from Settings and grant the scope it names. You do not need to grant everything at once.
An import was held
Spreadsheet imports run preview then commit, and the commit can be held rather than applied. Holds are deliberate and each names its reason: a tab that read far below its usual row count, a tab that read zero rows, or an overlapping sync already in flight.
Fix: open the review queue, confirm the change is intended, and release it. A hold means Suvi noticed something that looked like data loss and stopped. See importing a spreadsheet.