Skip to content

--- title: Troubleshooting Guide description: Step-by-step fixes for sign-in, cases, demands, negotiation, trust ledger, and portal problems. ---

Troubleshooting Guide

Fixes ordered from most common to least common. Each section follows the same pattern: symptom → check → fix. For one-line answers, see Common Issues and FAQ and the FAQ.

1. I cannot sign in

  1. Confirm the email spelling and password, then try again.
  2. If your firm uses MFA, confirm the code is current (codes expire quickly —
  3. generate a fresh one).

  4. If the page says the account is inactive, ask an admin to verify the
  5. account and resend the invitation if needed.

  6. Still failing? Clear the field autofill (managers sometimes fill an old
  7. password) and try once more before contacting support.

2. My invitation link expired or the wizard is stuck

  1. Invitation links expire — ask a firm admin to send a new one and use the
  2. newest link in your email.

  3. If the onboarding wizard seems trapped (for example on a 1-seat trial
  4. invite), go back to the dashboard and re-enter onboarding from there, or ask your admin to re-invite you.

3. I cannot see a case

  1. Search Work → Cases by case number or client name to rule out a filter
  2. issue (clear named filters first — invalid filter input is rejected, so a leftover filter can hide results).

  3. Check with the case owner or an admin: you may not be assigned to the case,
  4. or your role may not allow access.

  5. Leads live in the leads inbox, not the case list — check there before
  6. assuming the matter is missing.

4. Room counts look wrong, or a room opened the wrong page

  1. Refresh first — room lists (/cases?room=…) match their counts, and IOLTA
  2. includes settled matters waiting on a debit, which surprises people.

  3. Opening a live matter from a room list intentionally lands on the next
  4. settlement move, not the overview. Only leads open the overview (to convert to intake).

  5. If counts still mismatch after refresh, follow
  6. Stale Version and Browser Cache Refresh.

5. Demand generate or send failed

| Error | Meaning | Fix | |-------|---------|-----| | 409 NO_STORED_MEDICAL | Medical file is empty | Add a treatment, bill, or record on the chronology page, then generate on /cases/:id/demand | | 409 CITED_SEND_REQUIRED | Sibling draft page cannot send | Move to /cases/:id/demand (the cited send path) | | 409 NO_RECIPIENT | No named carrier recipient | Fill in the recipient and send again | | 409 NO_DESTINATION | No destination | Fill in the destination and send again |

Remember: recording delivery marks the letter delivered but does not email, fax, or mail it. If the other side never got the letter, you still need to deliver it through your own channel.

6. I cannot log an offer, or settlement will not unlock

  1. Enter a dollar amount on every money event — amounts are required, and a
  2. $0 acceptance can never unlock Settlement.

  3. Log the acceptance with Log acceptance while the matter is negotiable.
  4. Changing a status dropdown, dragging kanban, or bulk-editing cannot settle a case — only a logged acceptance owns settlement status.

  5. If the room still names Log offer, log the outstanding offer or demand
  6. first.

7. IOLTA debit or reconciliation failed

  1. Read the ledger banner — it names the exact blocker (open liens, failed
  2. debit/recon, next step).

  3. TRUST_OPEN_LIENS: clear open liens in the lien tracker first. Reduced
  4. medical-bill and subrogation liens still block — clear them too.

  5. Overdraw refusal: debits cannot exceed the trust account balance or the
  6. client's case balance. Split the entry or correct the amount.

  7. Bank/book mismatch: the ledger never stamps reconciled on a mismatch.
  8. Recheck both balances and reconcile again.

8. A document upload failed

  1. Confirm the file type is supported (PDF, DOC, DOCX, XLS, XLSX, CSV,
  2. images) and the size fits your plan.

  3. Refresh the page and retry once.
  4. If it still fails, contact support with the document type, file size, and
  5. case number. Old revisions are safe at /cases/[caseId]/doc-versions.

9. A signature request went to the wrong email

  1. Void or cancel the request if possible.
  2. Correct the recipient email and send a new request — never reuse an
  3. incorrect signing link.

10. An integration says attention or blocked

  1. Open Settings → Integration Reliability for the exact provider error.
  2. Reconnect with live credentials, or ask an admin to update them. Stored
  3. stamps alone never count as connected.

  4. 409 PROVIDER_NOT_WIRED means that provider has no live wiring — it is
  5. not usable yet. Do not retry with the same keys; check the Integration Reliability page for which providers are live.

11. A report export looks short

  1. Re-run the export — exports stream the complete filtered set in the
  2. current release, so an old short file was likely truncated by the previous behavior.

  3. Check your filters: an extra filter narrows the set legitimately.
  4. Advanced reports stay behind a toggle — enable it first if rows are
  5. missing.

12. I see old data after a deployment

  1. Hard-refresh the page.
  2. If it persists, follow
  3. Stale Version and Browser Cache Refresh.

  4. If it still persists, report the page URL and the app version stamp from
  5. Settings/diagnostics to support.

13. Notifications or AI credits look wrong

  1. Missing notification? Check the notification list and sidebar badges,
  2. including bulk-read state — triaging with mark-all-read hides items by design. Portal messages arrive in the same thread staff answer from Communications Hub.

  3. AI credits low? Ask an admin to review usage and add credits. Avoid
  4. regenerating the same output repeatedly.

How to report a problem

Include all four: page URL, case number if relevant, what you expected, and what happened (exact error text like TRUST_OPEN_LIENS helps). Send it via the in-app help area or to your firm admin.

Source: docs/user/troubleshooting/troubleshooting-guide.md