Troubleshooting and warning reference

Resolve shortfalls, conflicting edits, mismatched reserves and connection problems.

A change will not save

Symptom	Meaning and next action
Conflict / stale head	Someone or another window wrote after your preview. Refresh, inspect Activity, then review a new preview before saving. Do not blindly repeat the old write.
Not enough to set aside	The source cannot cover the amount on that date or a later day. Check future-dated transactions; reduce the allocation or correct the date.
Balance assertion failed	The proposed change disagrees with an existing statement check. Inspect the named account and day; correct the transaction rather than removing the check to conceal a discrepancy.
Too many decimal places	Enter an amount valid for the commodity. Import is the only automatic precision-increase path.
Undeclared account or commodity	Check spelling and case and use a declared path or symbol. A parent account declaration is not inherited.
Server unavailable / writes disabled	Loaded data remains readable. Check the connection and sign-in; Kabacus retries and does not queue writes.
No Save action on an edit	An unchanged transaction has nothing to save and creates no revision.

Overview warnings

Warning	What to inspect
negative-fund	A reserve is overdrawn. Check its spending and source account before setting aside more.
negative-free-money	Reserves exceed the money available in their home account. Review allocations and bank transactions.
reserve-mismatch	The card reserve and card owed amount differ. Inspect Credit and missing reserve lines.
unreserved-unaccounted	Flagged card transactions do not explain the whole reserve difference. Look for standalone movements in the reserve.
unclassified	No account-kind rule matched. Check the path and the host’s rule table.
uncategorized	expenses:uncategorized is not zero. Categorize the relevant transactions.
duplicate-display-name	Two accounts have the same friendly name. Use paths to disambiguate them.
exclusive-assertion	An older money-account assertion excludes reserves. Review inclusive-assertion conversion with rewrite access before changing historical reserve lines.

Warnings draw attention to a problem but do not themselves block writes. Validation errors do. A successful save can therefore coexist with an unresolved warning.

File permission and browser recovery

After a browser restart, Chromium may need permission to reopen each file before editing. Other browsers use browser storage. If a file is refused, verify that it is a genuine .kabacus database from a compatible version; renaming an arbitrary SQLite file is not a conversion. Keep a copy before attempting recovery.

Report a reproducible problem

Record the application version, interface, operation, error sentence and relevant revision. Expand Details for technical context. Reproduce with synthetic books where possible and remove financial data, credentials and personal information before sharing logs or sample files.