Troubleshoot saves, imports, and recovery

Distinguish a connection problem from a refused change

Read the complete save message. A connection failure calls for checking connectivity and retrying through the displayed action. A refused edit can instead mean that a date, quantity, related record, or application limit prevents the change.

If another tab or device changed the company, preserve any unsaved input you need, reload the latest records, and reassess the proposed edit. Repeating the same stale form is not a way to merge concurrent changes.

Follow recovery prompts after an interrupted operation

If the app reports an unfinished change, follow its recovery and retry controls before entering new transactions. The app keeps recovery information for interrupted writes. Do not manually delete cloud keys to dismiss the message.

After recovery, inspect the intended result and History before recording the event again. If the operation completed, repeating an import, issuance, or exercise could duplicate it.

Restore a company from a JSON backup

In Settings, choose the backup import action and select a company JSON export. Review whether to Replace this company or import into A new company. Replacing changes the selected company’s working records; a new-company import creates and switches to another company.

If creation succeeds but importing fails, the dialog identifies the new empty company and allows retrying into that same destination. Check the company selector before starting another import. JSON backup import is different from the additive CSV importer.

Settings also lists restore points. Review the timestamp and label before restoring. Up to five points are kept, and size constraints can retain fewer; use downloaded backups for versions you need to keep independently.

Resolve common validation problems

• Award exceeds plan capacity: check its destination, effective date, existing commitments, and the actual adopted reserve.
• Exercise or settlement exceeds vesting: check the event date, schedule, prior claims, and early-exercise permission where applicable.
• Linked certificate cannot be edited: inspect its transfer, exercise, or conversion chain before correcting the underlying transaction.
• Import duplicates: securities are not automatically deduplicated. Inspect the preview before repeating the import.
• Missing attachment: check the Puter account and whether the backing file remains accessible. A JSON backup is not an archive of file contents.

When escalating a persistent issue, note the app action, exact message, company context, and whether it followed a restore or concurrent edit. Use a minimal reproduction without exposing private agreements or holder information.