Get back to a clear state
Check the connection, preserve the evidence, and recover deliberately.
No companies appear
- Confirm Tally is running on this Windows computer and the intended company is loaded.
- Confirm its XML server is enabled.
- Open Tally connection and choose Check again. If you need to change the port, expand Advanced: connection settings and choose Test and save.
- If several Tally endpoints are found, select the intended one. A running bridge alone does not prove Tally is ready.
The owner page is locked
Open the installed Tally Bridge shortcut again. Direct navigation does not authenticate you. Restarting the bridge invalidates owner browser sessions; existing paired app grants remain subject to expiry and revocation.
An AI app cannot connect
Check that the bridge is running, then inspect the app under My apps & permissions. Confirm its grant is current and includes the intended company. Restart or reconnect the desktop MCP client after configuration changes. Use the generated paths for this installation and Windows account. Revoked or expired grants need new approval.
A record changed before my edit
A version conflict means you need to fetch and review the latest record before deciding on another change. Do not discard the If-Match check. Tally can also be edited by another person or connector.
A write timed out or returned unknown
Keep the original idempotency key and operation ID. Inspect the journal entry, then reconcile that same operation using REST POST /api/v1/operations/{operationId}/reconcile or MCP tally_operations_reconcile. Reconciliation reads Tally and updates journal evidence; it does not resend the mutation.
Do not create a new key to “try again,” clear the journal, or assume an HTTP success proves the accounting write persisted. Preserve the uncertain state until readback establishes what happened.
An update cannot be verified
Leave the current app installed and try a later check from Updates. Unreachable, expired or untrusted update metadata blocks installation; the existing local REST/MCP service can remain available. Do not replace the private update history with an older backup.
An installer was interrupted
Keep the existing installation location and private state. Inspect the update result and installer log before recovery. Do not force-stop unrelated Node processes or Tally, automatically restore journals, or replay uncertain accounting work. Uninstall normally retains private state and backups; those files can contain business data.
Before sharing diagnostics
Use the owner Check this computer page. Review its output before sharing: network configuration can still be sensitive. Never share owner credentials, paired tokens, one-use sign-in links or private state files. Diagnostics describe observations; they are not an overall security certification.