---
title: "Troubleshooting"
description: "What each BareLedger error message means and how to fix it: self-approval blocks, repeated two-factor prompts, rejected uploads and stopped schedules."
url: "https://bareledger.app/guides/troubleshooting"
category: "Resources"
updated: "2026-10-29"
publisher: "BareLedger (Syneria Technologies OPC)"
---

# Troubleshooting

> When BareLedger says no, this guide explains what each error message means and what to do about it next.

### Symptom: A posting/reversal action unexpectedly asks for a TOTP code again despite an active login session

**Possible cause**: the tenant's security policy (`require_totp_for_review`/`_approval`/`_posting`, all default `true`) requires step-up MFA at that specific action, independent of the login session.

**Resolution**: this is expected behavior, not an error — enter a fresh code. If the organization genuinely wants to disable step-up, an Administrator can change the policy in Org Settings (subject to the email-OTP change-request confirmation).

---

### Symptom: A report or feature is completely inaccessible (not even read-only) after a plan downgrade

**Possible cause**: some plan-gated capabilities (Books of Accounts, statutory filings under `strict` feature-gate mode) block reads entirely when unentitled, unlike most write-gated features which stay viewable/exportable.

**Resolution**: this is intentional for derived reports with no underlying stored record to fall back to — upgrade the plan to regain access, or export the data before downgrading if you need historical copies.

---

### Symptom: A bank reconciliation session can't be edited

**Possible cause**: it's already `completed` (locked). Only the most-recently-completed session for that bank account can be reopened — older sessions can't, to preserve the opening-balance chain.

**Resolution**: use **Reopen** on the current session; if it's not the most recent one, you'll need to reopen sessions in order back to the one you actually need to change.

---

### Symptom: A file upload is rejected

**Possible cause**: exceeds the 10MB attachment cap (5MB for avatars/logos) or isn't an allowed MIME type.

**Diagnosis**: check the specific error message — the app-level limit (10MB) is stricter than the infrastructure limits, so app-level validation is what you'll actually hit.

---

### Symptom: A recurring schedule stops generating new documents

**Possible cause**: it hit a DST-ambiguous or nonexistent local time and flipped to `needs_attention`, which requires a human to call the resolve-DST action with an explicit instant — it's never auto-resolved.

**Resolution**: open the schedule's run history and resolve the flagged occurrence manually.

---

See Logging & Monitoring for where to look first when diagnosing an issue not covered here, and [Security](https://bareledger.app/guides/security)/Integrations for the specific failure-mode details behind each gateway/service.